There are a lot of communities I’m interested in that I know exist; if I visit them on their home-servers, they’re loading and whatnot; however, I can’t see them at all from partizle (and just get a 404 if I go to /c/name .ml
).
For example, https://kbin.social/m/rust should be reachable at https://partizle.com/c/[email protected], but the latter link is just a 404. Is there some background process for federation that’s broken? Are we intentionally defederated from kbin.social and lemmy.ml?
Yeah, it’s not ideal. You have to copy and paste the URL on the remote server (eg,
https://kbin.social/m/rust
) into search, wait a few seconds, and then it shows up as a search result. From there, you can subscribe to it.I can’t imagine why it works like that, but that’s how they made it. 🤷♂️
Definitely not ideal.
To add to this, my own workflow that has worked is this: when you initially search it will say “No results.” It gives no indication it is doing anything, but if you wait this message will go away. Then you can search for just the community name itself (no instance or punctuation) and it will show up.
It’s maddening that sometimes this works and sometimes you just need to wait a few hours and try again. It feels like some kind of federation background thread is stuck or some queue is full.