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?
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.
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?
You’d have different domain names to get people used to the concept. John Doe would sign up, and become [email protected], Jane Doe would sign up and become [email protected]
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.
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?
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.
i like the idea of a server choice virtually invisible feature!
Let me see how you get instance admins to agree on what to defederate.
Maybe a vote of 75% minimum would be good?
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?
You’d have different domain names to get people used to the concept. John Doe would sign up, and become [email protected], Jane Doe would sign up and become [email protected]
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.
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.
Basically, a single instance
Where?
When you go to comment on a blog, where do you sign up?
Man, it feels like you guys haven’t spoken to a real human in decades…