Asklemmy

The people behind Feddit have made their own community browser.

I encountered this while trying to set up my community subscriptions on lemmy.world, which is a very new server and had few people subscribing to remote communities when I joined. Here's my comment outlining the behavior:

https://lemmy.world/comment/1692

Summarizing:

• Federating with a remote instance does NOT seem to add all it's communities to your local instance's list. Immediately after federation, most communities will be missing from /communities/ on the local instance, and keyword searches on the local instance for the community will return no results.
• Searching for a community using its url or bang-prefixed-id causes the local instance to "discover" that particular remote community. It now shows up in /communities and keyword searches.

Also, as others have mentioned, there's https://browse.feddit.de/ for a distributed community search, though it seems to take some time for new communities to show up there. As an established instance, I also find lemmy.ml's community search useful for discovering communities even though that's not where my account is. "Most" big communities have been added to it's list by someone organically searching for them by bang-id or url.

I'm not 100% certain yet how federation works with lemmy, but I'm assuming it works similar to how it works on Mastodon and Calckey, only with group actors.

In that case, servers don't share all of their content with each other wholesale. Someone on your instance would need to already be subscribed to a community on another server in order for it to receive content from it, or to even know it exists.

In order for people to see content from actors (ie people or groups) that aren't currently being followed by someone on their server, actors they do follow need to boost that unshared content. And I'm not sure how that works on Lemmy.

To subscribe to communities that aren't currently being shared with your server, go to their home server, find the community there, get the community's URL, and then enter that into the search bar on your instance.

Because every instance fetches other instance's communities when you first type that name in a search.

It means, when you search for "[email protected]" (mind "!" at the begining), you should reload page after some time and search again. In that period your instance will fetch it from midwest.social and show in community search.

This question is more suited to [email protected] - see rule 3

To add to the other answers, when you search for the community that isn't registered yet, it will take 10 seconds or so for it to appear in the search, slower than everything else. You also have to type out the full name to register it.