Not able to see/subscribe to some communities from here?
Hello,
I have subscribed to a few communities already (some on other instances, like lemmy.ml ou beehaw), but some communities cannot be accessed from here, even tough other communities from the same instance are available.
For those in similar cases, you MUST first search the community in the search bar here.
Searching !golang@lemmy.ml only returned this thread initially, but after a few seconds the community appears in the search results.
From there, the community will sync here and will be visible here, with new posts appearing over time (afaik it doesn't sync existing posts, only new ones).
Hope this clears up the process for the next persons in my position :)
The community list syncs "lazily", only adding a community when a user tries to interact with it.
So at any given time, your instance knows about the list of communities that you and other users on that instance have searched for.
Communities in the list can be easily subbed.
Missing communities have to be "taught" to the instance with a very precise search.
This makes community discovery frustrating. There are some external community discovery resources, life gets a lot better when you use them... but you still have to do the dance about "teaching" your instance about a a new community when you're the first to find it.
It would be nice if this was configurable. Or maybe someone enterprising can write a script to do some searching now, while our usage is low, and the number of external communities is also low.
I know as things start to get really high usage, and the number of Lemmy instances grows, and communities per instance grow, that it might be untenable. But at least for this early onboarding process where we expect a lot of new users, it would be cool to give them a soft landing experience
More federated communities were showing up for me last night vs today. I’m thinking it’s a lot of new users bogging both ends down. There’s a lot of growing pains, but I think things should be sorted out eventually. No one was really ready for all of Reddit to onboard
Right so for a slightly deeper explaination, I was here about a week before the main wave so I got a pretty solid explaination from the old community
But essentially our instance doesn't know about any communities that no one on our instance has subscribed to.
Once someone has subscribed to it from this instance, it just gets added and everything is cool.
What will happen over time is people will find this problem increasingly rarely since sh.itjust.works members will have already subscribed to most of the important or interesting communities
You might already know that so I'm going to leave this here for anyone else who wants further explaination