this post was submitted on 12 Jun 2023
18 points (100.0% liked)

sh.itjust.works Main Community

7694 readers
1 users here now

Home of the sh.itjust.works instance.

Matrix

founded 1 year ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] Orygin@sh.itjust.works 9 points 1 year ago (14 children)

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

[–] sauce@sh.itjust.works 2 points 1 year ago (8 children)

I tried this with !motogp@lemmy.world and it never returns, I’m guessing Lemmy.world isn’t federated yet?

[–] Orygin@sh.itjust.works 2 points 1 year ago (6 children)
[–] sauce@sh.itjust.works 1 points 1 year ago (2 children)

Interesting, got a 404 last time I tried that. Thanks!

[–] PriorProject@lemmy.world 5 points 1 year ago* (last edited 1 year ago) (1 children)

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](/c/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.

[–] Klaymore@sh.itjust.works 2 points 1 year ago (1 children)

I found that just searching for the URL works as well (as long as type is set to all)

[–] PriorProject@lemmy.world 1 points 1 year ago (1 children)

Yeah, I just learned that today when making this comment. For the longest time it never occurred to me to set it to all... since.. like... I'm definitely searching for a community. But lemmy disagrees I guess.

[–] Klaymore@sh.itjust.works 2 points 1 year ago

yeah it took me a while to even register that those buttons were important lol. Hopefully it can get polished up a bit

It could be that the instance was down/overloaded. For example, I have been trying to connect to selfrepair@lemmy.ml today, but lemmy.ml is down. I can see and comment on existing posts from lemmy.ml though, so I'm interested to see how that works once it's back on-line (i.e. will it eventually show up?).

Good luck, maybe try again later! FWIW, I do see that community now, so I guess it got cached when @Orygin accessed it.

load more comments (3 replies)
load more comments (4 replies)
load more comments (9 replies)