Replying to @⁨MrWrinkles@leminal.space⁩

This would be more of a use case for blockchain, any site(/user) wishing to mirror the social media would participate in the chain. A post on one site would get pushed into the chain and show up on every mirror.

Media would likely have to be links outside of the blockchain since it isn’t usually very good at storing large datasets (it would make it difficult to mirror over time as it grew), so if you wanted a full mirror you would probably have your site fetching media as soon as it is posted and mirroring it yourself.

Or media might be a good spot to integrate with your bittorrent idea. Blockchain handles the distributed state of the site (communities/post text+metadata), and any submitted media is added to the post as bittorrent hashes. I don’t know how scalable bittorrent clients are though it might take considerable overhead to seed millions of pictures/videos.

Replying to an earlier post

Isn’t a “more correct” description of BitTorrent that each client is also a server? I’m not sure exactly how the protocol is written, but I assume each connection acts like a client-server one depending on the direction of data flow. With that in mind the fediverse is distributed social media. There’s nothing stopping you from spinning up an instance on say, your phone, making an account on it and federating with the other instances you like. Now your phone is both client and server, just like in BitTorrent. This setup would even match the functionality of only seeding when on. If you turn off your instance it would go offline and any non-federated data would not hit the web until you booted it back up, aka started seeding again. Defederating would act like removing a torrent from your list. Multiple users per server is where I think the analogy begins to break. Not sure what the BitTorrent equivalent would be.

Edit: Maybe SoulSeek is a better parallel??