Lemmy.ml is blocking all requests from /kbin Instances

barista@kbin.social to /kbin meta@kbin.social – 299 points –

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

125

It's possible that this is a consequence of the latest Lemmy update, in which a lot has changed. I have noted that kbin has some issues with request signature in communication with certain instances. I will try to check it tomorrow first thing in the morning.

Wow, thank you for the quick communication. Amazing aptitude. Almost nowhere else do you find a lead dev in the comment trenches letting us know what's happening, I'm kinda baffled.

Those links are working fine. Kbin is federating well with those instances. A bit of latency is normal.

No upvotes, comments or boosts go through

It takes time. I just setup my own instance and I sent a comment from there, it took 40 minutes to arrive on kbin.social, upvotes and replies have not made it back to my instance yet some 45-60mins after they happened.

It takes time
Why?

Because, when you post here from kbin.social any other instance with kbinMeta@kbin.social will get a copy of that and vice-versa. But each side is exchanging posts from multiple magazines to multiple other instances. It's also balancing resource usage for people visiting the site too.

Also new instances are gradually fetching the back-catalog of posts for various magazines (and communities on lemmy). So all of this leads to a delay.

Anecdotally the delay is quite short this morning. Yesterday it reached up to 2 hours from my view at least.

I don't understand why the delay is so high thought.
I just downloaded several GB in a few seconds, what is stalling the process that when only a few bits of information are exchanged? That seems unnatural.
I am severely underestimating the bandwidth load?

Well, there's a bit to unpack here. When you download something in seconds that's your whole connection to a server that is on a super fast connection.

Most people running instances are on a much more modest combination of hardware and connection and even the bigger ones (kbin.social etc) are not going to have a connection as fast as dedicated download CDNs can offer. I would expect they probably have a gigabit, and at most 10gbit. That's shared between everyone on the site downloading cat pictures, posting, refreshing AND the federation of all the new content to and from other instances.

But that's really not the problem here at all. Far more of a load is the processing of the incoming and outgoing messages to and from many instances. This takes CPU load (and to a lesser extent memory), and this is shared between the message queue for these inter-instance messages, the web server and database.

When you look at how the fediverse of kbin and lemmy is laid out. You will see there's a handful of larger instances with most of the popular magazines/communities. This means that they're doing the lion's share of this processing. Couple the fact that the population has exploded over the last month or so, even these larger instances might be struggling with hardware and/or infrastructure layout (maybe running all on one box, and needing to split the load for example). That's speculation though.

At any rate, for whatever reason (maybe the lemmy problems backing up message queues with errors) things were MUCH slower last night.

Case in point, it took less than a minute for this to reach my instance (this is me, posting from my instance... Maybe I should have used another username... This one has a picture, is the instance me).

Still after 5 hours.. the upvotes are behind.. I hope AP will scale well in the future.. This since looks not great.

But the oldest comments both there and on kbin.social are more than 55 minutes old without appearing in the respective other place.

Until kbin.social servers are fully upgraded, such delays will occur. Even afterwards, it might happen if the other instance is running on slow servers. We are still in the early stages of this platform, and there is no huge corporate throwing money at us (it is so early that there hasn't even been an actual 'Release' yet). These quirks are to be expected as kbin develops.

I've noticed we are also not federating with lemmy.wtf for some reason, maybe it's something related. They are connected well with other lemmy instances but kbin can't get a hold of them despite being on their list of linked instances

If they don't want us to communicate with the users of their server, they should be defederated. Sucks for the users, but they can hop to another server whose admins don't break communication inelegantly and ghost admins who want to know what's going on.

If it's just a bug, then obviously we should wait for it to be fixed, but if they're not even saying they'll look into it, I don't have much hope.

Before assuming, has anyone...asked them?

Before assuming no one has asked them, let’s read the post

“Yes, people have already tried reaching out to the Lemmy instance admins in their Matrix room with no answer.”

Ok, but, as the thread over there says, it's not like they're singling out kbin as far as the code shows. Just because no one there has answered yet doesn't mean they've refused to answer. Give it some time or some actual replies before assuming the worst.

Also that edit was added after my question.

It's been a few hours, this is way way too fast for the pitchforks to come out.

Code and config is different, it’s irrelevant if it’s not in the git.

If I use a firewall to block kbin in user agent then it doesn't matter what code is running, it will throw 403.

Edit: Just checked out, the first request with kbin user agent, it doesn't have x-powered-by: Express, suggesting that it is blocked in nginx level, it doesn't even reach the backend Express. This will not be reflected in the code whatsoever.

 ~  curl -I --user-agent "notKbinBot v0.1" https://lemmy.ml/u/test
HTTP/2 403
server: nginx
date: Wed, 28 Jun 2023 01:50:53 GMT
content-type: text/html
content-length: 146
vary: Accept-Encoding

 ~  curl -I --user-agent "placeholder-user-agent" https://lemmy.ml/u/test
HTTP/2 200
server: nginx
...
x-powered-by: Express
...

Yea this is bad. Lemmy.ml is actively blocking on 'kbinbot' (case insensitive) string in the user agent request.

$ curl -I --user-agent "this is KBINBOT" https://lemmy.ml/u/test
HTTP/2 403
....

$ curl -I --user-agent "this is KBINBO" https://lemmy.ml/u/test
HTTP/2 200
....

$ curl -I --user-agent "this is BINBOT" https://lemmy.ml/u/test
HTTP/2 200
....

According to the edit in the main post, yes, they have been asked.

Relevant question on Lemmy.ml, in addition to prompting on Matrix is here: https://lemmy.ml/post/1563840

Yeah, I posted that to !fediverse@lemmy.ml from my lemmy.ca account. I figured that if the admins aren't answering questions via Matrix or whatever, maybe someone there would have an answer. (So far, nothing more than the same kind of speculation that's happening here.)

In the spirit of a thriving fediverse, I suggest not to assume the worst of other parts of it before we know a bit more of what's going on.

At first I thought it was maybe a config error to block bots. But after some testing I see that the 403 is only given when the word "kbinbot" is in the user agent. String that just return the normal response I tested are "testbot", "kbinbo", "binbot".

Maybe it is some kind of automated rule 'block bots that cause lots of traffic'. kbin is becoming more and more significant, so it probably causes some non-insignificant load on Lemmy servers. Legitimate load, but the IDS rules would not know that.

I think the approach of changing the user agent in the interim is a good solution, if there's a technical reason they don't want kbin traffic they can be adults and reply in the chat, not just sneakily blocking incoming traffic

Doesnt surprise me, the developers of lemmy (which are owners of .ml) have an agenda. They are into censoring on ukraine news, and other stuff. I dont get why people are choosing lemmy over kbin when they are equally bad looking

Wait why is kbin bad looking?

It looks better than reddit.

yeah, kbin is probably the nicest looking reddit alternative i've seen. Really sleek design without leaning into the overly overly mobile-focused watered down New Reddit bs, while also not nearly as hideous as old reddit.

I do wish kbin looked a bit better on mobile, though. I have larger font on my iPhone and instead of wrapping, the text just goes off the screen and can't be viewed.

IMHO Kbin actually looks better on my mobile than on desktop.

I have both set to the aqua/greenish theme and on mobile my upvotes/interactions show up bright yellow...but on desktop there's no difference. Even if I take off "follow desktop personalization theme". (firefox for both.)

I'm glad you think so. Please see the attached screenshot for an example of what I'm talking about. I'd like to have the text one size bigger so I can read it more easily, but then whole words are cut off or missing.

Its a huge downgrade from reddit in terms of visual quality. But im soeaking on mobile safari so i guess that will explain alot but anyways heres what i see.

The posts that have pictures dont really show that well until you click on it. You need to scroll down a whole thread to comment on a post. Creating a post/thread is confusing, its hard to navigate “magazines” (idk why theyd call it that), theres a lot of problems with it.

Lemmy looked pretty bad on mobile safari, far worse than kbin

Eh? What are you talking about? There's literally a bunch of Russia and Ukraine news at https://lemmy.ml/c/worldnews. This rumor mill needs to stop. People started some bad rumors about Lemmy devs just because of their political association and now its blown up into full lies.

I use both Lemmy and Kbin, but I prefer Lemmy for a bunch of different reasons:

  1. Interface is cleaner and more performant.
  2. Getting to your list of subscribed magazines in kbin is a pain in the ass. Why is it buried in Settings?
  3. Kbin votes are public. This is just bad for privacy. It's one thing to say that votes are public due to federation, and whole other thing to blatantly show it in the UI. There's a reason why voting at a government level is kept secret, just sayin'.
  4. Also why the hell are they called magazines? None of the names in kbin map to existing conventions. "Threads" are posts. "Magazines" are communities or groups. I never get used to it because it isn't natural to call these things the way kbin calls them.

I wouldn't really call it "rumors" when you can go directly to the horse's mouth:

https://www.reddit.com/r/communism/comments/cqgztr/fuck\_the\_white\_supremacist\_reddit\_admins\_want\_me/

https://web.archive.org/web/20230626055233/https://old.reddit.com/r/communism/comments/cqgztr/fuck\_the\_white\_supremacist\_reddit\_admins\_want\_me/

Hey all, longtime Marxist-leninist, recorder of left audiobooks, and megathread shitposter here.

Posting this in light of a recent one week Reddit ban I earned for shitting on US police, as I'm sure many of us have gotten in recent weeks.

So I've spent the past few months working on a self hostable, federated, Reddit alternative called Lemmy, and it's pretty much ready to go. Unlike here we'd have ultimate control over all content, and would never have to self censor.

Obviously as communists, we agitate where the people are, so we should never abandon Reddit entirely, but it's been clear to all of us from day one, that communities like this stand on unsteady ground, and could be banned or quarantined at any moment by the white supremacist Reddit admins. This would be both a backup and a potentially better alternative. Moderation abilities are there, as well as a slur filter.

Raddle isn't an option obviously since it's run by this arch anti tankie scum, ziq.

I wanted to ask ppl here if they'd like me to host an instance, and mod all the current mods here.

My concern is with this line: Obviously as communists, we agitate where the people are. I'm pretty left-leaning myself (I draw the line at authoritarianism though), but they're very open about using their platform to push an agenda.

That post was made by the founder of Lemmy and the instance they mention at the end became Lemmygrad (because lemmy.ml and Lemmygrad are the same people - the ".ml" in "lemmy.ml" even stands for "Marxist-Leninist").

With Lemmy.ml as the "main" instance, you're exposing all these posts to an admin team who has openly said "we are agitating for our views wherever the people go, and we have ultimate control over all content." They have already removed posts critical of China as being "orientalist" (which shows a severe lack of understanding of what "orientalism" even is - it's not "anything that criticizes our Dear Leader"). I can't trust that any community hosted on lemmy.ml is free of bias.

It isn't "rumors" when you can clearly go and back it up with a source.

(FWIW - I don't mind Lemmy as a platform. My Lemmy account is actually from 2020, before I realized what they truly were. The maintainers have done a good job of keeping politics out of the software, and the concept of only using "ethical" things is a myth when your computer has rare earth elements in it. As far as instances go, Lemmy.world seems fantastic and has grown to be far larger than the tankie instances. But Kbin is more fully-featured and has a lot more long-term potential, even though it's lacking in the short-term.)

Sounds like youre spewing a lot of bullshit or intentionally misguiding. Read the thread below you and youll see.

I think liking an internet post and voting for the leadership of the government are not suitable for comparison here.

2 more...
2 more...

There is a question about this up on lemmy.ml here:

https://lemmy.ml/post/1563840

At least they're equally as confused, hopefully this is just an issue in communication and the federation of content will be back in full swing soon

Hey Yote.zip is saying this. What's up with that?

" I’ll add that I have recently noticed that practically nothing that I post has been getting through to kbin."

Relevant issue for gracefully handling 403 errors is here

Ahh 2023 the year of the great reddit, Beehaw, and Lemmy exodus

If this is intentional, I have to wonder why they're doing it in such a troublesome way rather than defederating properly. If they want to defederate, so be it, but then just do that.

This approach only makes sense as a blanket defederation of all kbin servers. Seems shady.

Well, lemmy.ml is the lemmy devs. Kbin is a competitor to their software. They might hate that Kbin is growing really fast and I think is overall better than straight lemmy.

I think it's more likely they just disliked the fact most Kbin users don't support genocide, while Lemmy has a history of that. The Stalinist side of Lemmy, moderated and endorsed by the developers, has made fun of Kbin.social before

It would be pretty against the spirit of ActivityPub if this were the case. Holding out to actually hear from them on this, hopefully, rather than assume such bad things about them.

They just recently had a software update I believe, so hopefully it's just a side effect of that.

Nah, probably just a configuration error on their end. Let's not jump to conclusions.

Lemmy devs aren't great people anyway, in terms of who you want to be developing software. Anyone that would think hardcoding word censorship into their software because it's theirs has a few screws loose, so I wouldn't put it past them to have done this intentionally.

Because "clever" authoritarians do the "isolating their people" kind of thing veeery quietly and not loudly.

Happy to see this. I've been avoiding .ml anyway, this makes my job easier. Fuck the Lemmy devs.

I suspect it's nothing more than an overeager web application firewall (WAF) blocking the requests automatically.

has anyone message lemmy.ml admins to see what may be up? maybe this is a bug rather than outright blocking

Yes, folks have tried reaching out in their Matrix chat without luck so far.

I was almost ready to say that maybe they're just looking for "bot" in the UA. But, no. It must be "kbinbot" anywhere in the UA, and case insensitive. So, pretty deliberate it seems.

Lemmy is no different than Reddit. They silence and ban anyone they don't agree with and do not care about the users.

You're making one hell of an assumption here.

Most likely it is a misconfiguration or bug. Or misunderstanding.

I don't think it's assuming anything to say that they deliberately blocked user agents containing the text "kbinbot" (case insensitive). I think it's fairly clear that's exactly what has happened here. Instructions to test as many variations as you want yourself are right in the main post in the thread.

Now, what we cannot say is whether it was done with malicious intent. There's some plausible reasons they might do it that are not malicious.

I think it's assuming a lot to say the things I replied to.

I was more replying to the second paragraph. It's a pretty deliberate configuration choice on the web server.

Ideally it's a config error at the firewall. I saw an interesting idea posed on the lemmy post suggesting that it may have been targeted by a DDoS that used kbinbot in the user-agent string.

Ultimately, it's not happening at a code level, it's absolutely happening at a firewall level (nginx, which, for those who don't understand, is kind of acting like the door lock on your apartment building, where you need to go through the main security before you can get to your own place. Sort of the same idea here). I just spent a bunch of time testing a bunch of various user-agent strings, and it very specifically is matching "kbinbot". No wildcarding within the word, but it a string like "blahbinbotblah" will 403, whereas "blahkbbinbotblah" won't (and various other forms, like k.bin.bot, or kasdfbinasdfbot.)

It's pretty specific. Anyone who deals with firewalls in any capacity understands how nginx works, and specifically why they and others are raising an alarm.

So yeah, ideally it's a misconfiguration, otherwise it's a fairly clear message.

  • assert "no different"
  • list one single, disputable similarity
2 more...
2 more...

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.

If this continues, my instance may need to defederate from Lemmy.ml.

That probably isn't the right fix for the long term, because otherwise it leaves kbin vulnerable to being DoSed by another instance intentionally returning 403s, or breaking down if something goes wrong with a lemmy or kbin instance that causes it to throw errors for totally innocent reasons. Kbin should be fixed to handle getting 403s reasonably-gracefully.

EDIT: Also, might be a good idea to check lemmy's handling of getting 403s as well for the same reason.

EDIT2: I don't know if lemmy/kbin have any kind of test code to test how well they deal with federated servers malfunctioning, but my guess is that using one set of tests for both would probably save effort.

They also do not sent POST / updates to my /f/inbox instance anymore. Lemmy.ml seems to activity ban Kbin instances. Which is very bad. I really hope this is not on purpose..

Check the instance list of Lemmy.ml, many seems to be missing version numbers. I don't know if it is relevant.

It's possibly an overreaction to the bot problem.
People started defederating suspicious instances, but what exactly count as suspicious is up for interpretation.
It's also very possible that was the point of the bot signups all along.

And on a relatively unrelated note, splitting the already minuscule fediverse, will kill any chance for it to become a real alternative.
Even if Lemmy's dev political views can be outrageous to some people, defederating them would be the beginning of the end imo.

Outraged feelings aren't the problem. Nobody is complaining about defederating Nazis. Defending and lying about Stalinist atrocities is morally no different from defending and lying about Nazi atrocities. If you let Nazis and tankies overrun your communities they won't be a "real alternative." Just like with Nazis, tolerating intolerance is intolerant.

You don't have to go as far as Stalin. The main lemmy dev has Dessalines as an handle.

I understand where you're coming from, but that uncompromising stance will probably mean we'll get corp owned platforms and that will be the end of it.
If I'm proven wrong on that ground, I'll apologize, but I genuinely doubt I will.

We would stand a chance if we made the platform neutral and let users decide whether and how they want to interact with assholes.

The issue is, it's only "kbinBot" and variations of that that don't work. If you just use "bot" itself, everything works fine. So it's not just an overreaction to the bot problem, unless all bot instances impersonated kbin.

The more likely answer is that lemmy.ml wanted to exclude kbin users from participating, but without actually limiting the freedom of their own users (which defederation would do).

And on a relatively unrelated note, splitting the already minuscule fediverse, will kill any chance for it to become a real alternative.
Even if Lemmy's dev political views can be outrageous to some people, defederating them would be the beginning of the end imo.

The current situation is misleadingly confusing to the average user and kbin moderators can't do their job properly.
I don't see how defederation, especially when temporary until the issue is fixed, harms anyone when we already can't interact properly anyway. I think the current situation is more harmful. Imo this sounds like the kind of situation defederation exists for.

defederation, especially when temporary
It will create ill will. Perhaps first have kbin's instances admins try to contact the dev.
And if they're unresponsive after a reasonable time then assume bad intent. Or maybe call them out publicly?

If Lemmy's dev them are actually trying to shadowban kbin, yeah fuck em, it would be evil behaviour.
But that would be a serious setback since lemmy has metcalfe's law running for it.

I think dissolution is one of the most obvious and dangerous vectors of attack on the fediverse (along with flooding and the classic embrace and extinguish), so we should keep that in mind.
Not to let paranoia take the better of me, but there are huge financial and political interests rooting against a free, transparent social media platform.

I think I had similar issues with one of the mobile clients using my Beehaw account, whenever I tried to write a reply I'd get a 40X (not sure which one exactly) error. I didn't pay attention to the server the post was on though but Beehaw being still on the .17 version might mess with other instances & clients in weird ways.

I've noticed this too. While I can post on a lemmy.ml community from kbin, I can't see it show up on my lemmy account.

Just confirmed the problems by running the curl commands locally.

Well, checking this post from my Lemmy instance (lemmy.sdf.org), it appears to be in sync with what I see from my Kbin instance (fedia.io).

Does that imply that whatever issue was in play here has been fixed?

This issue is specific to the lemmy.ml instance. So lemmy.sdf.org should not be affected.

If the lemmy devs start blocking kbin by adding code, it would be time to fork the code.

If you guys need a United Nations of sort, this is going to get messy.