this post was submitted on 14 Nov 2024
426 points (87.4% liked)

Fediverse

28380 readers
1051 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 48 points 1 day ago (6 children)

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] 2 points 13 hours ago

Basically, a single instance

[–] [email protected] 25 points 1 day ago* (last edited 1 day 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 1 day ago

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

[–] [email protected] 1 points 15 hours ago (1 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?

[–] [email protected] 1 points 12 hours ago (1 children)

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]

[–] [email protected] 1 points 12 hours 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.

[–] [email protected] 2 points 12 hours ago* (last edited 11 hours 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.

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

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

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

When you make an account

Where?