Search

So this has happened on a couple of my posts, but when I saw it affecting @gabe's recent intro post, I thought I'd call it out here.

Here's a screenshot - first image is of how the post looks when you're not logged in, the second is with login:

https://imgur.com/a/lRMP9yf

You can see even though there's two comments listed as being present on the 2nd shot, no comments appear.

So to determine whether this was client side or server side, I tested it out on multiple browsers and got the same result, indicating it's not a client side issue, and it's not related to my kbin extension scripts on Firefox. I can't find any settings within my profile that would affect this (if there's one I'm missing, please let me know).

For reference, here are the two of my posts that I'm finding the same behavior on:

https://kbin.social/m/13thFloor/t/332463/Untitled-by-at-Aphelion-at-mastodon-sdf-org

https://kbin.social/m/13thFloor/t/329335/Untitled-by-at-literarypug-at-mastodon-world

Thanks in advance for your help - I'd like to be able to both promote content and leave a review at the same time, but this bug is making it difficult. Note that this only appears to affect Threads, not Links at the moment.

EDIT: appears to affect Pictures as well, and is currently occurring on this post below. Gonna add @ernest so he has a heads up.

Additional testing shows that it's only affecting newer posts - posts older than two days ago don't appear to be replicating the behavior.

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