3 ms·
As a counter example, there are millions of non-technical users using the bittorrent protocol. They are running a server on their machines and not aware of the
by jeswin 9y ago
As a counter example, there are millions of non-technical users using the bittorrent protocol. They are running a server on their machines and not aware of the technical complexity that lies underneath. I am not saying it's an easy UX problem to solve, but it can be done.
- AsyncAwait 9y agoSure, I think the problem with people running i.e. Mastodon on their own machine would be what should happen when people turn off their computer. I guess there could be some sort of "super node" solution, where a known Mastodon server would just forward you the "what happened while I was asleep" stuff and I guess people could encrypt their messages to you with your advertised public key, so that you don't have to trust the super nodes, but I am not sure about the additional complexity involved in implementing that vs current Mastodon using ActivityPub, nor about the usability challenges involved.
- NoGravitas 9y agoThat's basically how Secure Scuttlebut works; the super nodes are called pubs. It's actually remarkably easy to onboard to SSB with Patchwork. The problems set in when you start considering mobile devices or multi-device support (the latter is currently possible but risky).
- fauigerzigerk 9y agoBitTorrent only works well (i.e in a true peer to peer fashion) if many people are serving up the same files so that some sources are always online. Outside of piracy that is rarely the case.
- icebraining 9y agoPeople will serve whatever the software wants; serving only want the user explicitly selected is just an option. For example, in Freenode you don't control what gets downloaded and served (which also helps to hide what you're fetching on purpose).