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 Really only issue I can think of would be changing the dynamic of trusting privacy of DMs from one entity to multiple, but that's already kind of a problem cross-instance anyway and a general weakness of Mastodon.


@kekcoin @shinobimonkey yeah that's true, but again people should just avoid non-e2e dms anyway, regardless of how/how many people run the instance

@afilini @shinobimonkey Eh. It's just another visibility setting to your posts. As long as you take the limitations into account they are a reasonably fine tool (though, admittedly, their presentation is likely to give the wrong idea).

Sign in to participate in the conversation
Bitcoin Mastodon

Bitcoin Maston Instance