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)

  • pre@fedia.io
    5·
    1 year ago

    Yep, look to me like it’s more than just the DDOS protection from kbin.social, no federated posts in “new” for about 24 hours now.

  • TheOneCurly@fedia.io
    2·
    1 year ago

    I agree, there’s some sort of federation issue or delay.
    I noticed earlier that content from news@beehaw.org is delayed, there are several new threads from the last few hours there that haven’t appeared here yet.
    And I can replicate your issue with the lemmy.ca communities.

  • Shdwdrgn@fedia.io
    0·
    1 year ago

    I haven’t even been able to connect to magazines on other kbin instances. I’ve been trying to sign up for !webcomics@kbin.social and !mycology@kbin.social since yesterday but I still can’t get either group to appear in the search from here at fedia.io. I also tried entering the full URL to those groups as the search (which is what works on lemmy). Maybe kbin needs a different format but I think the bang-names were correct here?

    • Michael@fedia.ioOP
      1·
      1 year ago

      I suspect those magazines aren’t showing up due to the DDoS protection that’s enabled for kbin.social. I think they’re still working on fixing the federation issues over there.

    • 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…