I’ve noticed in the explosion that we are getting duplicate communities in multiple instances. This is ultimately gonna hinder community growth as eventually communities like ‘cats’ will exist in hundreds of places all with their own micro groups, and some users will end up subscribing to duplicates in their list.
A: could we figure out a system to let our communities know about the duplicates as a sticky so that users can better find each other?
B: I think this is the best solution, could a ‘super community’ method be developed under which communities can join or be parented to under that umbrella and allow us to subscribe to the super community under which the smaller ones nest as subs? This would allow the communities to stay somewhat fractured across multiple instances which can in turn protect a community from going dark if a server dies, while still keeping the broader audience together withing a syndicated feed?
I think a simple solution to this problem would be to be able to integrate several subscribed communities into a single timeline, similar to Mastodon Lists.
I would call this feature ‘Mingling’ :)
There is no problem if there are more communities with the same topic. The ones wich are better moderated and actively updated will eventually gain in popularity and stand out
Maybe. But until then I need a possibility to aggregate several into one…
I don’t think this is an issue tbh.
The full name of a community includes the instance is running on. For this community here the instance is asklemmy@lemmy.ml . If you are referring to community you should include the instance to avoid confusion.
To the issue of duplicate communities: That issue existed on reddit too. Communities with slight variations in the name always existed. Sometimes the owners of some variation of the community just decided to forward their users to a “main community”. Sometimes multiple communities coexist. I believe that in most cases a certain “main community” will establish itself as the one that the majority just accepts as the “real deal” because it has the most activity and the best moderation policies.
A lot of duplicate communities arose organically though, to fulfill a new niche. Sometimes it was stuff like actual lesbians finding that /r/lesbians was a porn sub, so they made /r/actuallesbians.
I can’t think of any examples right now, but there are also definitely cases I’ve seen there the offshoot variations arose organically, diverging from the main community.
I’m not disagreeing with you, just wanted to highlight that many of the variations on Reddit weren’t the same, but smaller, but subtly different and thus catering to different communities (which may have overlap with the original). I worry that this kind of “speciation” won’t happen if the fragmentation remains too great.
A key aspect is that you could generally tell the difference between the offshoot subs by the name, which is harder with this instance model. For example, I don’t know what the deal is with /r/AITAH, but it’s fairly clear that it’s an offshoot from the main Am I The Asshole (AITA), so I can assume there was some beef. There’s also cases where a mass exodus from a sub is justified and the “primary” sub (most active users) is not the “original” sub. It’s just harder to tell these things from the name on Lemmy
It’s just harder to tell these things from the name on Lemmy
This is why I believe that it’s important to establish that people mention communities with their full name. For example when you talk about this sub here you use asklemmy@lemmy.ml and not just asklemmy or c/asklemmy or some variation.
I mean we are basically agreeing here. I just don’t think that this issue can be solved by lemmy itself. I believe we need to have the ability to create communities indepentendly on other instances. Otherwise the idea of lemmy would be pointless. This is an issue yes. But it’s an issue that can only be solved by the users. I have a (pretty much empty) Valorant community on here. I would be willing to close that community and have a pinned post telling people to go to a more active community. Maybe there could be a technical implementation to automate that forwarding or something idk.
