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

@afilini Could you tell me in which way this would be better than, say, all of those anybody*s just running their own instance?

@kekcoin I'd say for starters possibility of redundantly saving all the data for a single virtual "instance." Rather than having users/history black holed and vanish if one goes down.

Follow

@shinobimonkey @kekcoin anybody running its own instance would be ideal, but that's kind of unrealistic i'd say.

really what I'm trying to achieve is a way to distribute people who don't run their own instance across multiple smaller instances run by volunteers, making sure that none of them grows to the point where it can't be easily hosted "at home" anymore.

even better if those smaller instances can "look like one" (for the network effect), plus the benefits from replicated data

Sign in to participate in the conversation
Bitcoin Mastodon

Bitcoin Maston Instance