Click communities at the top. Then sort by all. That will be every community your instance has access to. If your instance blocks another instance then you won’t be able to see it.
AFAIK is every community your instance has access to that has already been accessed by someone in your instance.
What I mean is if someone creates a community in lemmy.one it won’t show up for anyone in lemmy.ml until someone manually searches for it or for a post in that community.
So it’s two part. The first is that federated communities have no central server. There is no way for an instance like lemmy.ml to know about all lemmy servers, because there’s no central server keeping track.
Instead, a server only learns about another server when someone on that server searches for a community on another server. As far as I can tell, simply searching for a community is enough to make it show up on your instance’s list of communities (assuming a valid community is found).
From my testing, adding one community does not automatically grab all communities. Only the specific community searched for will then show up under the Communities “All” list.
This is mostly just from my own testing running an instance. You can search more about how the fediverse works to learn more, there are always more posts trying to explain it (on of the biggest problems is trying to sell it as something different instead of focusing on the on-boarding process).
Click communities at the top. Then sort by all. That will be every community your instance has access to. If your instance blocks another instance then you won’t be able to see it.
Also for a global search there is https://browse.feddit.de
AFAIK is every community your instance has access to that has already been accessed by someone in your instance.
What I mean is if someone creates a community in lemmy.one it won’t show up for anyone in lemmy.ml until someone manually searches for it or for a post in that community.
Interesting, I would be interested to find a source for that. I’d love to read more
So it’s two part. The first is that federated communities have no central server. There is no way for an instance like lemmy.ml to know about all lemmy servers, because there’s no central server keeping track.
Instead, a server only learns about another server when someone on that server searches for a community on another server. As far as I can tell, simply searching for a community is enough to make it show up on your instance’s list of communities (assuming a valid community is found).
From my testing, adding one community does not automatically grab all communities. Only the specific community searched for will then show up under the Communities “All” list.
This is mostly just from my own testing running an instance. You can search more about how the fediverse works to learn more, there are always more posts trying to explain it (on of the biggest problems is trying to sell it as something different instead of focusing on the on-boarding process).