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 example, I cannot access !golang@lemmy.ml from here, even though I can access other communities from lemmy.ml here, and the community is accessible from other instances (like feddit.de: https://feddit.de/c/golang@lemmy.ml). I only get a 404 error: https://sh.itjust.works/c/golang@lemmy.ml

Is there any reason why? Maybe related to load issues @lemmy.ml?

  • Orygin@sh.itjust.worksOPEnglish
    0·
    1 year ago

    Ok, figured it out.

    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 :)

    • nLuLukna @sh.itjust.worksEnglish
      1·
      1 year ago

      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

    • PriorProject@lemmy.worldEnglish
      1·
      1 year ago

      Sounds like you’re sorted, but for more context check this post out: https://lemmy.blahaj.zone/post/61827

      TLDR:

      • 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.
          • PriorProject@lemmy.worldEnglish
            1·
            1 year ago

            I find that searching by community string never actually returns any results. It’s essential to make the search in order to add the community to the communities list, but you don’t find anything useful that way.

            But AFTER doing the community string search, I can do a keyword search and it works. So each of these searches is from the communities page on the instance where you have your account…

            1. Search motogp, get no results because the community isn’t known to your local instance.
            2. Search !motogp@lemmy.world, get no results… because… I dunno. Because we can’t have nice things is why.
            3. Search motogp again and it works because now the community is known to your instance.

            I though the blahaj post was giving this same advice, but their steps are subtly different. Try the above if the sticky posts advice doesn’t get it done for you.

            Edit: I just tried the blahaj instructions and they DO work for me. Searching the bang-prefixed community with the “type” constrained to “communities” (or anything other than all) returns nothing. But searching the bang-prefixed community string with types set to “all” does return the community. No idea why it doesn’t get returned when constrained to communities, seems like a bug.