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.

  • CosmicSploogeDrizzle@lemmy.world
    5·
    1 year ago

    I’m not sure if this specifically applies, but there are federation issues happening across multiple instances.

    Many issues have to do with a mismatch in Lemmy BE versions. Lemmy.ml is on 0.18, others are on 0.17.4 waiting for Capcha support to come in 0.18.1. BE 0.18 replaced websockets with http, so it’s a substantial update. How this works with kbin specifically I do not know, but things are in flux.

    Additionally there is this issue:

    https://github.com/LemmyNet/lemmy/issues/3101

    Which according to the devs is related to this other issue that has been fixed and will also likely come in 0.18.1

    https://github.com/LemmyNet/activitypub-federation-rust/pull/52

    So, I do not believe this is international. If lemmy.ml didn’t want to federate with kbin they would just defederate. With kbin being its own distinct software that is different than Lemmy, these issues are likely due to the drastic change in the last Lemmy update. Things will have to be ironed out between kbin and Lemmy

    • Skull giver@popplesburger.hilciferous.nlEnglish
      1·
      1 year ago

      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.