From the UI perspective, I’d like to use https://github.com/fossasia/open-event-frontend/ . Working on this could also result in a reusable ember-holochain adapter
Some screenshots:
This is more focused towards groups. The booking part could be either a separate app or part of the admin section. The nice thing about holo is that you can install two apps and work on the same data, can’t you?
Alright, y’all, invite sent for Thursday at 2:30 pm UTC.
Splitting the difference @friedger, because it’s early in the morning for me and I want some sleep : ).
Look forward to seeing y’all then!
My bad, didn’t see Viktor’s comment about availability. Rescheduled to next Tuesday at the same time, that work for y’all?
good with me… got a lot going on but will definitely drop in… i see some very useful patterns emerging
In the medium post about the terran collective and Hylo they also state that included in the high-priority features they are working on is:
Events: public and private options, ticketing, attendee lists, communication with attendees and community calendars.
maybe someone from there is useful to have in the conversation? @bear
Love this idea!
The vision you shared in the HackMD document is great. I appreciate your focus on design! Here’s a an article I really love that might be interesting or helpful to you around getting to a minimum testable > minimum usable > minimum lovable product.
https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp minimum testable product
For me and this app, considering minimum testable… I wonder how quickly you could build something for a user to create an event, have all users see the events and have other users be able to join an event. Thoughts?
This is a good question and idea. I’ll do some checking to find out who that might be, though, if they’re in California, the time we’ve scheduled is going to suck for them.
Most of them are in California Bay Area. But they’re a large enough group that is is possible some might be traveling. I’ll reach out for you and connect with Bear to ensure all deets are detailed. 
It would be cool if it has functionality like Kickback, where you have to register with some kind of currency and then you get the money back if you attend (plus a percentage of the money of people who didn’t show up). This allows the even to still be free but have some skin in the game if you don’t show.
So I spoke with Aaron from Terran Collective and their priority is to keep the old communities and central platform going, so they’re not going to building anything with Holochain for at least 6 months, but, they’ll be sharing things they build with our community to build relevant backend parts on Holochain starting soon, so that’s where the possible connection point is.
It’s true that the events module is one of the priorities in the their log, so they’ll be working on the centralized version of it in the not-too-distant future. Aaron expressed interest in this project and I invited him to the meeting next week to get connected.
Looking forward to it.
Interesting. Nothing indicating that they’re looking to move things in a more open direction, unfortunately/not-surprisinglingly-
By extension of, and in addition to, this thread, a highly complimentary hApp would be co-working space management, AKA “HoloWork” – a mutual-credit-enabled, distibuted WeWork alternative.
I am working on a meetup variant, but instead of physical meetups, it will be based on virtual/webrtc meetings. Lots of fun and still have tons of stuff to do. Hopefully the MVP will be production ready within a couple of months.
My (long term) goals are:
One of the things I would like to play with, is how statistics and (open) data can be visualized within the app itself. Just to give users another way to navigate and contribute to making sense of meta stuff.
Currently, I am bootstrapping and looking for people to have a look when the web-app is ready. If you are interested, please use this form:
The initial app will be created on centralized tech. If people find it cool; use it and are willing to fund/collaborate to build a bridge to Holochain. I am all ears
My plan with groups is to add this later. Mucho complexity and it would make sense to MVP with individuals. An individual could start a group in the future…for now, an account could be a person/individual or an organisation with single credentials.
@AdriaanB It is a very opportune time to create a virtual meetup platform! Something the world needs right about now. Sounds like you’ve got some exciting stuff planned there.
Sounds brilliant Adriaan! Are you building it with MongoDB?
According to Arthur Brock, a centralised app would be easier to “port/convert” to Holochain later if its based on MongoDB…
I am using Postgres for now, since I have a lot of relational data (social network part). My experience with MongoDB is that it becomes a mess when trying to mimic a relational database. But maybe these days it became easier…
I don’t think I will port the whole app over to Holochain but will be looking into hybrid solutions. For example, each event/session will have a chatroom (ala Zoom) and this could be created/ported over to Holo&Holochain. Also interested in reputation systems and even payments. Not there yet, tho
you could write a dHapp that utilizes smart contracts, chances are many of them will except they can function more expansively and efficiently. Holo is different because of the P2P nature of network communication. In software terms, It is a light weight client that is infinitely scalable. There can be hybrid applications where only maybe a part of, or a specific feature needs to use the advantages of DHT (distributed hash table) or other distributed hosting advantages. I could see alot of early dHapps offering SaaS
Yes definitely because there is alot of room for network customization. basically think about it as we are rebuilding the internet from scratch lol and with alot better technology available these days. each Holoport is your piece of what used to be a centralized server
These are very good questions you’re asking. Its up to the developers (and not just coders, everyone is a developer, everyone should contribute ideas!) What rules of reputation do you think are effective? How do we appropriately measure and distribute value as a collective? The good thing about Holo is there will be tons of access to metadata like we’ve never had before, with plenty of options to protect it. We’re going to be able to do alot of cool stuff with data and IoT.
How to avoid spam? Biometric logins would be helpful. Either way, the network can warn you of misbehavior within the membrane and then your account could be set to automatically warn your friends and block interaction. There are people working on these solutions. A big challenge (as always!) is DDoS and Sybil accounts
Validation could apply to alot of different concepts. Holo does not validate transactions because it does not require consensus. The dHapp you write or choose to use, could implement validation in a variety of ways. Within the core of Holo itself, there is validation of entries onto the DHT, its more of a coding term than a blockchain one. So again, you could further implement types of validation or authority rules. It’s basically like a file manager in a broad sense.
Ex:
@friedger event dHapp wants to use a voting system or some type of ratings given for reputation, but wants to make sure that only certain accounts can vote/rate. those could be approved admin (can even require photo ID) or they could be members that have reached a certain level of participation status etc
you could also keep 2 metrics - one only the admin see and one all members see
perhaps some community members votes are more weighted than others
the options are endless
dont worry its not like every dHapp developer has to invent this stuff, there will be plenty of libraries to use. if you see a reputation feature that works, then go ahead and plug it in!
the Holo community is very collaborative. in the near future, we’re gonna have a bunch of open source tools to make the dev life easier
group entries into types (categories or authority level) and have editor_role_of. entry_type<entry_hash>
