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?
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.