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.
The websockets were never part of ActivityPub. That’s purely part of the server <-> client API.
kbin and lemmy are interoperable but the internal version mismatch between Lemmy instances has nothing to do with kbin.
There are a whole bunch of bugs in the standard deployment based on the manual. The nginx.conf issue you listed is one I noticed myself when I followed the manual. These issues are probably trivial to solve for the Lemmy devs as they have in-depth knowledge of ActivityPub, but server admins probably rely more on premade configuration files.