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?

[–] gregor@gregtech.eu 3 points 2 days ago (3 children)

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?

[–] Rentlar@lemmy.ca 2 points 2 days ago (2 children)

You'd have different domain names to get people used to the concept. John Doe would sign up, and become john.doe@apple.server.hostname, Jane Doe would sign up and become jane.doe@banana.server.hostname

[–] gregor@gregtech.eu 2 points 2 days ago (1 children)

This is quite unnecessary, it would be simpler if we have a list of the long-running and most stable instances and have the users pick one.

[–] Rentlar@lemmy.ca 4 points 2 days ago* (last edited 2 days ago)

That is what we have now, but clearly people are averse to making a choice that they are not technically inclined to know how big or small the consequences of that are. My solution is a spitball one with obvious flaws, but essentially it is that the instance is picked randomly out of a group of very closely, if not identically aligned servers.

load more comments (8 replies)