I believe more and more people will escape to lemmy sooner or later, and I already see 3 different communities for the same thing (selfhosted) here on lemmy. Time will tell which one will be the most active, but lets assume all of them will be equally active and the desire emerges to combine the two communities about the same thing, is that something possible or intended to be possible with federated services?
True, but they are all with different names, and they are not completely the same (as in different rules, more specific topic vs general topic, etc). But on Lemmy there is a possibility that two communities having the same exact topic and name for example [email protected] and [email protected], they are both discussing technology (and not any specific difference between them).
@SafetyGoggles The difference between those two is the moderation policies of the instance. Beehaw doesn’t federate with the same instances that lemmy.ml does, and has an explicitly more inclusive and less generalist approach. They both cover the same ground, but you couldn’t just merge them.
Having said that, it would be nice to see a user level feature that lets end users combine communities in to one “virtual” community in their interface.
@g7s @DudePluto
The down side of that would probably be duplicated content. Like if some major news happens for a topic reposts can already be really annoying and usually need moderator action to combine threads. Then there’d be that times however many communities exist for that same topic.
Yep, that’s exactly what I mean. Coverung the same ground, but they are different communities with different moderation, so it can’t be merged, but it make sense to group them together and view it as a “playlist”. Just like Whitney Houston and ABBA don’t collaborate to make albums, but it make sense for their songs to exist together in a playlist called “Songs from the 80s”.