this post was submitted on 23 Aug 2023
77 points (98.7% liked)

Fediverse

28724 readers
110 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 2 years ago
MODERATORS
 

cross-posted from: https://sh.itjust.works/post/3508135

There's been an ongoing debate about whether communities should combine or stay separate. Both have significant disadvantages and advantages:

Combine:

  • Network effects. Smaller communities become viable if they pool together their userbase. Communities with more people (up to a point!) are generally more useful and fun.
  • Discoverability. Right now, I might stumble on a 50 subscriber community and not realize everyone has abandoned it for the lively 500 subscriber community somewhere else, maybe with a totally different name.

Separate:

  • Redundancy. If a community goes down, or an instance is taken down, people can easily move over.
  • Diffusion of political power. Users can choose a different community or instance if the current one doesn't suit them. Mods are less likely to get drunk on power if they have real competition.

This isn't an exhaustive list, but I just want to show that each side has significant advantages over the other.

Sibling communities:

To have some of the advantages of both approaches, how about we have official "sibling communities"? For example, sign up for [email protected] and, along the top, it lists [email protected] as a sibling community.

  • When you post, you have an easily accessible option to cross-post automatically to all sibling communities. You can also set it so that only the main post allows comments, to aggregate all comments to just one post, if that's desirable.
  • The UI could detect sibling cross-posts and suppress multiple mentions of the same post if you're subscribed to multiple sibling communities, maybe with a "cross-sibling post" designation. That way it only shows up once in your feed.
  • Both mod teams must agree to become siblings, so it can't be forced on any community.
  • Mods of either community can also decide to suppress the cross post if they feel it's too spammy or not suitable for cross discussion.
  • This allows you to easily learn about all related communities without abandoning your current one. This increases the network effects without needing to combine or destroy communities.

Of course, this could be more informal with just a norm to sticky a post at the top of every community to link to related communities. At least that way I know of the existence of other communities. I personally prefer the official designation so that various technologies can be implemented in the ways I mentioned.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

How does moderation work in this scenario? Does it fall to instance admins to moderate, and defederate/ban anyone who is causing problems for the global community? That seems like it would amplify the moderation burden significantly

[โ€“] [email protected] 1 points 1 year ago

If you use it as a submission process where each community recieves it in their submission queue for approval (which possibly could be processed by something like automoderator) then you could make it much smoother. The individual community wouldn't show anything they don't want, and act essentially like aggregators of links to threads.

Also, they can then similarly hide comments in threads as viewed from their community (also possibly via something like automoderator).