As title state, is the bridge broken? Or it’s by design?
thank you
I see a kbin post in my lemmy feed 6 spots below this one. [email protected].
It’s left behind 21 days in lemmy, than in the kbin.social site, 3 hours ago.
Is it by design ?
There’s been a few posts about lemmy.ml seemingly blocking kbin traffic via user agent header
Interesting… only the main instance is blocking kbin traffic. Thanks for the heads up!
It’s not blocked at all. Maybe it’s a configuration problem, I don’t know.
Edit: It was actually blocked and I wasnt aware of it. Now its unblocked.
Try checking it out through another instance.
Yeah from your instance it’s working perfectly https://lemmy.dbzer0.com/c/[email protected]
Only lemmy.ml. hmm… Seesm WAF
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
I think lemmy.ml was blocking kbin a while ago, should be fixed by now, not sure.
This has been reported in post/comments, but never with convincing evidence to my knowledge. Nutomic (dev and lemmy.ml.admin) is in this thread reporting that there’s no blocking in place and they don’t know what’s up.
No. I see it as current, not behind 21 days. A bug maybe?
you are using /c/[email protected] right?
When I go to that page, last thing is 21 days ago, or because I’m not succesful following? Ugh…
Archive is also show 21 days ago… ugh…
Yes, I have full and normal access to that very mag from lemmy.world, seeing content produced today, not weeks ago.
I think federation with kbin will always be a little bit wonky. It’s a completely different application at the end of the day. It’s like how Mastodon instances are federated with Lemmy, but you can only see so much content that way.
This is more of a support question - please see the sidebar for suggested communities.
It never worked for me.
