I have this weird idea for a distributed and private Mastodon instance:

- the instance would be Tor-only
- anybody* could help host an instance they like by installing and running some software (let's say a "node")
- the nodes would connect with each other and coordinate which one should do what (storage, database, http, etc)
- by using OnionBalance one can split the traffic among all the "http" instances

*not really "anybody" because this would make it trivial to take down the instance

but if we change the trust model to a federation with a strong "leader", then it basically becomes pretty similar to what we have here today, with the added benefit that the admin doesn't have to carry all the costs of running the instance

if the traffic is sufficiently spread around, then it could potentially become feasible to host the entire instance outside of the cloud, avoiding any kind of "deplatforming"

@afilini how about a message board client that reads/writes to IPFS? Someone has a project like this called "boards": github.com/ipfs/awesome-ipfs

Follow

@rusticbison i'm not a huge fan of ipfs myself because it doesn't really replicate data unless many people download a specific file. i guess it would work, but I'd try with something else first if possible

@afilini from a UX standpoint IPFS is also really slow and often unreliable. Maybe webasm w/ local storage in the browser is better, especially if you don't try to persist content forever.

Sign in to participate in the conversation
Bitcoin Mastodon

Bitcoin Maston Instance