Apologies if I’m just doing something wrong, but I seem to be having patchy results loading up communities from other instances.
E.g. this works fine: https://aussie.zone/c/[email protected]
On the other hand, this gives 404 community_not_found:
https://aussie.zone/c/[email protected]
(And it definitely exists, see here: https://lemmy.world/c/music )
Any ideas?
I searched for
https://lemmy.ml/c/movies. First time, nothing. Second time it showed up. I think lemmy.ml is just overloaded.Hmm, maybe I’m just misunderstanding exactly what you mean by ‘searching’. What was the URL of the search page when you did the search? E.g.
https://aussie.zone/search/q/...(or is it even of that format?).Hmm something odd is going on. Searching for
moviesshows the community, but for the fullhttps://lemmy.ml/c/moviesURL does not.Yeah, and searching communities for
movies@lemmy.mlalso gives nothing at all.Okay so I’ve been able to get communities to load after (but not necessarily as a result of) spamming a mixture of their full URL (e.g.
https://Lemmy.world/c/music), their URL without the protocol (e.g.lemmy.world/c/music) and just the community name by itself (e.g.music). The results always turn up on just the community name by itself.I’m thinking the most likely explanation is that the communities are found by incrementing through the federated instances, and the time it takes is just highly variable (probably due to server load, and possibly the order in which instances are polled?) and my spamming the various formats I mentioned above is simply a way to keep myself occupied while I wait 😆