2y ago

What do you think is the best solution to having the same named communities on different instances?

We should implement this as whenever I wish to browse (for example) technology@lemmy.world I have to go to there, and whenever I wish to browse technology@kbin.social I have to go there. Would it be possible to implement it in kbin/lemmy's code to make it easier to browse all?

You're viewing a single thread.

45 comments

This is an issue I've been wondering about, the Technology example is fine, but the real edge case IMO is Official Communities.
Like, let's say I have an Android App and want to migrate my official community to Lemmy. I could build a community in:
A big and general instance to gather more users, like Lemmy.World.
A big but themed instance, like Lemdro.id. It has a smaller number of users but they are more likely to be interested in my App
I could make my own instance, which would allow me to dedicate communities into topics and I would have more control over it, which is good cause it is an official community.
I feel there should be a way for "sync" communities in those cases. It makes sense in those cases to allow a full sync, with the option to unsync if things go south and there's a split.
- I think for official communities self-hosted instances feels like a win-win for everyone. Companies get full control of their community but no one has to participate with it in isolation. They can also separate discussions, eg news@pokemon.com or blueprints@factorio.com.
  For more abstract themed communities lime technology it's definitely more complex. Reddit's partial solution is multi-subreddits which could apply here but it's far from a complete solution.
  
  The issue with that is that an user could be on a popular instance, like lemmy.world or a related one like lemdroid, and search for a community on it. They could find a ghost community that was created unofficially before the self-hosted one. In that case they could think this is it and there's no real discussion to be had on Lemmy.
  It is also slightly weird because there's an incentive for developers to grab the appname@popular.instance to ensure they can use the name and link it to the official instance. But that also leaves a ton of pretty much barren communities.
  That's why I think keeping in sync would be a good feature, keep all communities in sync with the official one so that users aren't lost.
  That said, this only works for official communities, and maybe(huge maybe) regional communities that have a self hosted instance
  
  The practical solution for that, is to simply search the topic you are interested in plus lemmy on google. Chances are best that you will find the most active community.
  Since reddit's search feature was completely unusable for the majority of its history, for me that is just "business as usual". Though it would be nice to have a more integrated solution.
  
  Alright but what if there was an active community that moved to a self hosted one? Wouldn't that still show the older community first?

45 comments