Thanks everyone for the help.
Original post: I want to create a niche community, but considering Lemmy can’t see kbin magazines, wouldn’t it make more sense to make the community on Lemmy, that way people from both Lemmy and kbin can be a part if it?
Maybe I should have posted this on a nostupidquestions community, I don’t know.
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.