4 ms·
What I would prefer is a set of protocols that are interact in a well defined way with each others, like the Email or Usenet protocols, then you can write diffe
by orbifold 6y ago
What I would prefer is a set of protocols that are interact in a well defined way with each others, like the Email or Usenet protocols, then you can write different clients for these and decentralisation is just a matter of running different servers clients that don't necessarily interact with each other. Something like the CapeProto RPC framework makes it relatively easy to declare the interface of a service.
- finder83 6y agoI'm curious if Skynet or something similar could be used for that? I don't pretend to understand any of the modern blockchain frameworks, but a peer-to-peer distributed and encrypted system seems to fit the bill (possibly non-blockchain related, I'm not sure). It was trending yesterday: https://news.ycombinator.com/item?id=25710151 https://news.ycombinator.com/item?id=25710151
- redsolver 6y agoSkyFeed is a decentralized social network built on top of Skynet: https://skyfeed.hns.siasky.net https://skyfeed.hns.siasky.net
- mawise 6y agoRSS and Webmentions[1] do this pretty well on otherwise ordinary websites. The protocols exist, we just need to make them easier to use for non-engineers. [1]: https://indieweb.org/Webmention https://indieweb.org/Webmention
- berkes 6y agoIsn't activitypub, webfinger (and therefore HTTP etc) just that?