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 fediverse@lemmy.world and, along the top, it lists fediverse@lemmy.ml 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.
That's an interesting proposal. I think I need to understand it better. Could you describe to me in what ways this would be better?
With the way things are set up right now, a community is centered on a server. This means that if that server goes down, your community disappears. If someone else creates the same community elsewhere, the community is split. If you're on server A and community is on server B but you're defederates then you can't participate at all, even if person on server C would be ok with you participating.
If the community was a Commons then no single server going down could eliminate the community. Individual servers could have mods for their portion of the community so each local community would have control over what they see and if the local community trusts other local community mods then that could be outsourced. Regardless, servers can get what they want to see -- gaming at exploding-heads and gaming at hexbear could coexist in a superimposed state, and servers that are kosher with both extremes would see everything, servers that are kosher with one extreme or the other would see what they're comfortable with, and servers not comfortable with either extreme could see nothing from either while still having a unified community regardless.
This sort of decentralization is why the broader fediverse works well. Lemmy as it currently operates isn't really decentralized since the majority of the power is aggregated into a limited number of servers who have the popular communities.
Very good point