Folks that have been here awhile probably already know this, but may have forgotten and new folks may not know it, so a reminder that we build the All feed together:
These previous ways will only show communities that are already known to the instance. Especially if you joined a small or inactive Lemmy instance, there will be few communities to discover.
With that in mind, for intrepid explorers here, I’d highly recommend looking for communities via Lemmyverse and joining them from here to make the All feed more varied than just Lemmy.World’s communities.
I post this as I was browsing through All the other day and noticed it looked like I may as well have remained browsing Local for how few remote communities I was seeing. And that’s not for a lack of interesting communities on other instances either!
Although...
…That’s not to say it might not also be due to a lack of activity in them, but that can be helped by looking for communities first before making them locally, I think!
Doesn’t always work tho. Opening https://kbin.social/m/[email protected] for examples gives me a 404.
I’m not too familiar with Kbin, but does it work similarly in that if nobody there has searched for that community, it may not show up to subscribe to?
In other words, if you search its url: https://lemdro.id/c/android on Kbin, does it show up as a magazine to subscribe to/follow?
https://kbin.social/d/lemdro.id also gives a 404.
Just checked if lemdro.id possibly defederated kbin.social, but that’s not the case. Could be that they have the same bug lemmy.ml had that blocks all requests from kbin instances.
@ElectroVagrant Yes it works like that on kbin, at least to an extend. I am not sure when exactly it gets available tho. Besides that, as other people said, there seems to be a federation bug at the moment which seems to cause this problem.
I read that the admin is fixing that soon.