"That is kind of terrifying," he suggests.Ĭapsule would seek to route around the risk of mass deplatforming via "easy to deploy" P2P microservices - starting with a forthcoming web app.
"When you deploy Capsule right now - I have a prototype that does almost nothing running - it's basically one binary. And you get that binary and you deploy it and you run it, and that's it. It sets up a server, it contacts Let's Encrypt, it gets you a certificate, it uses SQLite for the database, which is a serverless database, all of the assets for the web server are within the binary," he says, walking through the "really nice technical idea" that snagged $100,000 in pre-seed backing insanely fast. "There are no other files - and then once you have it running, in that folder when you set up your capsule server, it's just the Capsule program and a Capsule database that is a file. And that is so self-contained that it's embeddable everywhere, that's migratable - and it's really quite impossible to get this level of simplicity and elegance so quickly unless you go this route.
So given how many protocols already offer self-hosted/P2P social media services it seems fair to ask what's different here - and, indeed, why build another open decentralized standard? Then, for the mesh federation thing, we're just doing HTTPS calls and then having decentralized caching of the databases and so on."Īmong the Twitter back-and-forth about how (or whether) Kobeissi's concept differs to various other decentralized protocols, someone posted a link to this XKCD cartoon - which lampoons the techie quest to resolve competing standards by proposing a tech that covers all use cases (yet is of course doomed to increase complexity by +1).
0 kommentar(er)
