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 was thinking the idea of hashtags at the community and/or post level could be an idea. That way it could aggregate the various communities on instances under one umbrella. E.g. https://lemmy.ml/#gaming could bring up every federated and indexed community tagged gaming. A community such as the pokemon one on lemmy.ml could have tags #pokemon and #gaming in order to appear both at the superset of gaming as well as connect with other pokemon related subs if there was pokemonGo or pokemonTCG.
It would likely require an update of lemmy system itself, I’d have to spend a lot of time with the code to get an idea of how to implement it.
This is how it’s done on mastodon
I was also thinking it would have the plus of better integrating with mastodon and other ActivityPub apps that use hashtags.
I’m a terrible coder and I also won’t have any chance to even start figuring out Lemmy until at least Tuesday night.
This would be lovely. Then once that functionality was working, we could create a Reddit-style front-page for new accounts that subscribed to a bunch of popular hashtags. That would really help to ease onboarding and make instances feel a bit less isolated.