!minimalism@lemmy.world Is the latest one I’ve found. I can find it if I go to my instance in the web, but not within the app.
The first time someone on an instance enters the name of a community, is when the instance goes and looks for it. Until then, that particular community is not federated to the local instance, and it is as if it does not exist.
Searching for a community in Jerboa, does not seem trigger this establishing of a connection.
Yep, sadly that happens, currently I just go to my instance’s website, search it there (wait a few seconds because it takes a while) and subscribe there. I’ll see it reflected in Jerboa soon enough.
I’ve noticed the same on the web UI. Searching a non-local community more often doesn’t work than does.
Search by community URL instead https://lemmy.tld/c/community
I’m on latte.isnot.coffee and I just searched both
!jerboa@lemmy.mlandhttps://lemmy.ml/c/jerboaand didn’t get results for either. Neither has a message saying that there are no search results, but neither shows any results either.
Search by the URL
https://lemmy.ml/c/jerboa, it’s faster, if you search byjerboa@lemmy.mlthen you need to search again but only the community namejerboaLike here “Method One: Search by URL”
https://tech.michaelaltfield.net/2023/06/11/lemmy-migration-find-subreddits-communities/
I can sometimes get them to populate if I do it twice or change it from Communities to All in the search filters. Other times, it just takes an extra 5-10 seconds after returning no results.
I’ve seen both of those behaviors as well, but more often than those, it just never displays results.
I’ve found this mainly happens when trying to search for communities on other instances
I’m guessing this arises from that community not being shared with your home instance yet? Or some similar desync issue.
