In the past weeks lemmy.ml was activity blocking all /kbin instances by looking at the user-agent string “KbinBot” (case-insensitive). Which causes quite a few problems on several /kbin instances, because lemmy.ml didn’t want to federate with ‘us’.

Recently, Lemmy.ml removed this block so it started federating again, at least so we thought.

Today it seems that Lemmy.ml is block all /kbin instances again:

curl -I --user-agent "kbinbot" https://lemmy.ml
HTTP/2 403
server: nginx
date: Thu, 06 Jul 2023 20:02:34 GMT
content-type: text/html
content-length: 146
vary: Accept-Encoding

Lemmy developers or the community never responded to any of our questions or request for clarification about this matter.

Ps. I know lemmy.ml is not ‘whole Lemmy’. However, Lemmy.ml instance is hosted by the official Lemmy developers (Dessalines and nutomic) and considered one of their biggest instances.

@lemmy.ml Please, can you be transparent about the reason why? Could we help you maybe?

  • gk99
    4•1 year ago

    However, Lemmy.ml instance is hosted by the official Lemmy developers (Dessalines and nutomic) and considered one of their biggest instances.

    It’s also a tankie instance that has dished out bans for speaking negatively about China’s government and genocide of the uyghurs.

    We don’t need to legitimize lemmy.ml and beg for federation just because it’s run by the creators of Lemmy. They clearly don’t want us, I don’t really believe the rest of the fediverse really needs them. I recommend instead directing new users to either kbin or one of the countless well-run Lemmy instances and avoiding lemmy.ml communities in general, so that pointless defederation on their part only hurts them.