Hey... that just gave me a small idea... what if we made a "flock" or "herd" of Mastodon servers? The group of servers would all federate with each other, have the same block and allow lists, moderation policy and teams spread throughout them.

When you make an account you can be assigned a random instance name within the flock. If your instance goes down you could still possibly log in using other servers? Main benefit would be spreading server costs and maintenance effort and de-centralized operating, but still keep a centralized feel to it?

[–] [email protected] 1 points 31 minutes ago

Basically, a single instance

[–] [email protected] 1 points 2 hours ago

If they have the same people running all of them, how is that different from running a single mastodon server in kubernetes, so that it doesn't get overloaded?

[–] Kbobabob 1 points 2 hours ago

When you make an account

Where?

[–] [email protected] 4 points 8 hours ago

Let me see how you get instance admins to agree on what to defederate.

[–] [email protected] 20 points 15 hours ago* (last edited 15 hours ago) (1 children)

Honestly that’s probably the best sort of solution. A group that has some minimum standards of moderation and maintenance/upgrade management plan and just evenly distribute the load as people arrive.

Then as a second phase make it easy to transfer, that way at the point the user gets comfortable they can easily swap to a better* “home” for those that care, for those that don’t, make the server choice be virtually invisible.

[–] [email protected] 5 points 14 hours ago

i like the idea of a server choice virtually invisible feature!