I discovered yesterday evening that Lemmy.ml is blocking all inbound ActivityPub requests from /kbin instances. Specifically, a 403 ‘access denied’ is returned when the user agent contains “kbinBot” anywhere in the string. This has been causing a cascade of failures with federation for many server owners, flooding the message queue with transport errors.
This doesn’t appear to be a mistake; it has been done very deliberately, only on Lemmy.ml. Lemmy.world and other large instances do not exhibit the same behavior. It also isn’t a side effect of the bug introduced in Lemmy 0.18. You can observe by sending the following in a terminal
> curl -I --user-agent "kbinBot v0.1" https://lemmy.world/u/test
HTTP/2 200
[...]
> curl -I --user-agent "kbinBot v0.1" https://lemmy.ml/u/test
HTTP/2 403
[...]
> curl -I --user-agent "notKbinBot v0.1" https://lemmy.ml/u/test
HTTP/2 403
[...]
> curl -I --user-agent "placeholder-user-agent" https://lemmy.ml/u/test
HTTP/2 200
[...]
Additional evidence of this not being a Lemmy 0.18 bug:
-
This occurs when making web requests to any location on the Lemmy.ml webserver, not just ActivityPub endpoints.
-
Go to https://fedidb.org/software/lemmy and pick an instance running 0.18.0. Perform the above commands, replacing the URL for Lemmy.ml with that particular instance’s address.
If this continues, my instance may need to defederate from Lemmy.ml. This is especially problematic because Lemmy.ml continues to federate information outbound to other kbin instances while refusing to allow inbound communication from them.
Spoofing the user agent is less than ideal, and doesn’t respect Lemmy.ml’s potential wish to not be contacted by /kbin instances. I don’t post this to create division between communities, but I do hope that I can draw awareness to what’s going on here. Defederating /kbin instances entirely would even be better than arbitrarily denying access one-way. This said, we should all attempt to maintain a good-faith interpretation until otherwise indicated by the Lemmy developers. It’s possibel that this is a firewall misconfiguration or some other webserver-related bug.
Relevant comment from me (#354 - [BUG] Critical errors/failed messages during messenger:consume)
Edits:
-
Yes, people have already tried reaching out to the Lemmy instance admins in their Matrix room with no answer.
-
Someone has posed a question on Lemmy.ml about the block here: https://lemmy.ml/post/1563840
I hope this issue is resolved quickly. It seems to be quite problematic.
Hopefully it’s a technical hiccup since every other option feels… shitty?
well, i don’t think the tankies liking their safe space being overload with “normies” decent takes.
just a speculation tho
Oh it’s a tankie instance. Not a big loss then.
Unfortunately Lemmy.ml was also the “flagship” Lemmy instance for a while, at least initially. I’ve got an account there myself because at the time I was signing up the only other large instances were offline for various reasons. I don’t use it much any more and would be fine with never using it again, but I bet a lot of people wound up on it and didn’t continue exploring further. So this is a bit of a mess and I would have hoped account migration tools would be better developed by now.
If that’s the case then they can shut it down and move to lemmygrad where at least they’re not pretending to be normal people. My biggest problem with lemmy.ml is that they will enforce their beliefs with “orientalism” bans without ever saying that this will happen if you post contrary to their stances.
Personally, I hope it’s intentional and leads to other places defederating lemmy.ml as a result, finally cutting them out of the mainstream instances.
I mean… They try to maintain some veneer of propriety but than daddy Stalin and Mao worship comes out.
Ask them about tianamen square… 🤫
If it is actually the case they are doing it for political reasons that its a good thing it happened now when Fedverse is in rapid growth and not a year from now.
Wagner.ml