this post was submitted on 10 Jul 2023
18 points (100.0% liked)
Moving to: m/AskMbin!
1325 readers
1 users here now
### We are moving! **Join us in our new journey as we take a new direction towards the future for this community at mbin, find our new community here and read this post to know more about why we are moving. Thank you and we hope to see you there!**
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Oh, maybe that's where I got the idea that Lemmy couldn't see them, I've only been on the fediverse for a couple weeks. People were saying Lemmy couldn't see kbin, but I didn't realize that was temporary.
There's some suspicion that the specific instance lemmy.ml is rejecting incoming requests from kbin via a configuration, but lemmy.world, lemmy.ca, beehaw, etc. seem to be federating well enough.
Not really suspicion at this point. They are proveably 403 rejecting requests from the KBin useragent. You have the letters "kbinbot" anywhere in your useragent (case insensitive) you ain't getting content.
As a bonus they're still sending out stuff to instances though. But since KBin can't then resolve it it amounts to a DoS attack as the messages just build up in KBin retry queues.
At what point do the other instances consider this federation in bad faith and defederate from .ml?
A number of kbin instances already have. But not .social - which is obviously the largest instance.
Aggravatingly .ml users can browse and interact with kbin magazines just fine as we let them in. It's very much a bad faith thing at this point.
Noted and I'll make sure that my list is clear of .ml subs. Honestly, with the "not so much rumors as facts" information swirling around out there about the devs, I'll not be surprised if they're intentionally tanking (pun intended) any competition that isn't parroting their views.
G'day from a Kbinaut :)