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?
The search function typically lists the biggest communities first, so the likelihood that a user will encounter a barren community first, is probably not that high.
Doesn’t it place higher the communities that are on the same instance as the user?
Theoretically it shows the communities with the highest subscriber count first.
Right now tho it seems, that Lemmy is bad at fetching the real subscriber counts of other instances. For example I get this result, when searching for Linux on this account right now.
Every sub-count besides the one of my home-instance is terribly outdated, thus it favors the home-instance community. This is probably not the intent of the developers tho.
I’m currently using Connect (the android App) and search is even funkier, to the point where it order is frankly random, and it appears to only show “famous” instances or the ones I’m subscribed to at least a community.
I know this isn’t intended, but I can’t help but feel that if sync was possible, this wouldn’t be a noticible issue