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.

  • IntlLawGnomeOP
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    Could be, for sure. I may try to post some things from Lemmy.ca to Kbin later. I was successful in posting from Kbin to Lemmy.ca a few hours ago, so I wonder if there’s a problem in the other direction.

    UPDATE: I was able to successfully post an article to kbin.social from my lemmy.ca account. It did take about an hour for the article to show up on kbin (when not viewed from my lemmy.ca account), but it did eventually show up.