I’ve been trying to subscribe to magazines/communities from lemmy.ca.

I recall seeing on kbin.social that people were having trouble seeing communities from lemmy.ca as well, but it was attributed to the DDoS protections that were enabled. From what I can tell, fedia.io does not seem to have the same protections enabled, but I still cannot see communities from lemmy.ca (e.g. I was able to find hockey@lemmy.world, but not hockey@lemmy.ca).

On lemmy.ca, it seems like fedia.io should be federated with them.

Does anyone have any guidance on how to track down the issue? Thanks in advance!

EDIT: After a few days of trying, I was finally able to discover hockey@lemmy.ca, vancouver@lemmy.ca, and toronto@lemmy.ca. (But canada@lemmy.ca still doesn’t work… Hopefully soon)

  • theinspectorst@fedia.io
    1·
    1 year ago

    I’m having the same problem. This needs sorting out quickly as it’s completely defeating the point of a federated model - kbin.social is the biggest Kbin instance and if we can’t see its magazines from other instances then they’re encouraging everyone to just sign up there instead - which they don’t seem able to accommodate anyway…