A post on kbinMeta states that “Lemmy.ml is blocking all inbound ActivityPub requests from /kbin instances.” More details here, but the theory is that – rather than defederating – lemmy.ml returns a 403 ‘access denied’ message in response to any inbound requests from a user agent with “kbinBot” in the string. Upvotes, comments, and boosts don’t seem to be going through. However, it appears that lemmy.ml still federates information outbound to kbin instances.
I’m wondering if anyone here knows what is going on and why it might be happening? Federation between Lemmy instances and Kbin instances seems to be a selling point for both, so I’m sure others using both services are curious as to what’s going on.
It is not a bug as it is blocking the specific user agent, it blocks all requests with that user agent even for things that cannot cause any incompatibility (like just querying user info from the command line). Also no other lemmy instance shows this ‘bug’, regardless of version. It is a very deliberate block either done manually or by an IDS.
Would be nice if a server admin would chime in, but it is very silent on all channels.