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.
I wish apps would hide duplicate posts. People that crosspost everything results in my feed having double everything because I subscribe to both. It's super annoying, and I'm tempted to leave one of them, but I don't want to miss anything because they're comparable in size.
I agree. I hesitated to cross-post this, but someone suggested I do so on the original post.
But that shows a structural problem with the user incentives on Lemmy. The norm of discouraging cross-posting itself means that we have a system that actively discourages people from connecting with others. And if we're actively incentivized to unsubscribe from multiple similar communities, that's even worse! These are the opposite of the sort of incentives we should have in a healthy and viable social network.
People often did similar things on adjacent subs (grilling, bbq, smoking).
It was annoying because I had them all in a single multi, but generally, only up voted or commented on the one that was already most active.
For that reason, I never cross post... I find it annoying, so I don't inflict it on others...
Though, now that I think about it, posting in one community, watching for traction, then if it doesn't pick up, cross posting a couple days later wouldn't be horrible.
Ok I get the message. I will refrain from cross posting as much as possible in the future. I do think this is not like Reddit and this tendency is a self-own for Lemmy where there is much more balkanization by design.