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)
There’re definitely federation issues. Nothing has shown up as new today since slightly before you posted. Here’s a thread that should be on lemmy.ml, but is actually just fedia.io people talking into the void.
https://fedia.io/m/selfhost@lemmy.ml/t/6093/Discord-AlternativesI wonder if lemmy.ml is having their own issues. For example, I’m getting a 502 as of this posting.
Noticed the same problem also with blahaj.zone, cloudhub.social, dbzer0.com, villa-straylight.social, burggit.moe, perthchat.org, pineapplemachine.com, midwest.social, bakchodi.org, links.hackliberty.org and lemmy.cloudhub.social
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.
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.Same here, trying to add /m/RedditMigration@kbin.social and nothing comes up. Is this an issue with Fedia, or the entire Kbin program?
I suspect that is due to kbin.social DDoS protection. I believe they’re working on fixing the federation issues.
I seem to remember the dev saying that it’s specifically related to the tier of the cloudflare subscription he’s got.
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?
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.
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…
I’ve noticed that if I exclude the exclamation marks, it usually shows up in the search. Usually. But even then it’s still only showing me stuff from 5 hours ago.