4 ms·
If I may shamelessly mention the project we've been working on the last 7 years... https://m.youtube.com/watch?v=pZ1O_gmPneI https://m.youtube.com/watch?v=pZ1O
by EGreg 9y ago
If I may shamelessly mention the project we've been working on the last 7 years...
https://m.youtube.com/watch?v=pZ1O_gmPneI https://m.youtube.com/watch?v=pZ1O_gmPneI
1. We started with the idea that actually social tools would let you get in, get out and get on with life. They would help you coordinate your actual social life in the real world instead of sucking up your time online. A minute spent on the app would result in hours socializing in the real world, not the other way around. Group activities would form like snowballs leading to an actual goal, not random chatting. Thus came the first part of our mission: Empowering People.
2. We also realized very soon that communities wanted to install our software themselves. The flipside of letting people actually get together on their own time, is that we can help unite their members and engage them. Universities and Buildings, for example, release their own social app to their Students and Tenants, and allow them to find one another and connect on their own time. (See https://qbix.com/communities https://qbix.com/communities). Thus we cane upon the second part of our mission: Uniting Communities
3. We realized there is actually no good open source alternative to Facebook, that communities can install the same way they can install Wordpress for blogs. We wanted to change the world and have developers and startups build social apps as easily as Wordpress plugins. We wanted communities to run our platform and apps even on a mesh network or router disconnected from the Internet - REAL decentralization, to be used in countries with censorship, or on a cruise or remote village to plan dinners, date, etc.
But the world has changed since blogs and we had to build and maintain literally thousands of features, from user signup to data access to payments. We recently got a security audit by an outside firm and are proud to say that they found (and since patched) only three, very hard to exploit, vulnerabilities in the entire platform. The code is at (https://github.com/Qbix/Platform https://github.com/Qbix/Platform). We don't have a slogan for this part of our mission yet :)
It's totally free and open source, and we will begin growing a community around it in 2018. If you want to join or find out more, contact me -- the email is greg and the domain is qbix.com
See a 7 minute video about it to understand fully the how and why:
https://m.youtube.com/watch?v=pZ1O_gmPneI https://m.youtube.com/watch?v=pZ1O_gmPneI
- visarga 9y agoWatched the video. I like how you think, we need more anarchy in the social web, each community standing on its own, no central arkhi (authority).
- walterbell 9y agoNice work. Which tool did you use to create the video? One of the examples says that when overlaying a Google map widget on the dentist's site, that the dentist does not have access to location data. Elsewhere, the video mentions iframes. If the dentist's web site runs HTTPS, how are you injecting iframes? Or is the primary "site" being served locally, with the dentist's web site displayed in an iframe? If all of the user's identity data is stored on their phone, how do they backup that data or move it between devices?
- EGreg 9y agoGreat questions. 1. I used Keynote and then ScreenFlow 2. The dentist's site HTML/JS actually chooses to include the iframe pointing to the user's identity server, our platform does the rest. 3. The user's data is stored encrypted in other areas, as well. They themselves can decrypt the data and grant keys to access it as they see fit. Our platform handles the rest.