Review on mailing list:

Copyright (C) 2026 Variscite Ltd. AI bot review and may be useless.

Copyright year is 2026, which is in the future. Should be 2024 or current year.

Great, now everyone will get to read useless AI agent reviews.

https://lore.kernel.org/all/20260303210131.2966214-8-Frank.Li@nxp.com/

I'm behind on reading LWN weekly issues, so I only now got to the article about the AI bot that flamed matplotlib mainainers. Choice quote: "We should note that LWN is still entirely written by people and makes its mistakes the old-fashioned, human-powered way."

Well said, @lwn

To anyone who thinks there is a systemd root privilege escalation vulnerability discovered recently. Please read the technical details instead of listening to idiots on youtube and reddit.

https://cdn2.qualys.com/advisory/2026/03/17/snap-confine-systemd-tmpfiles.txt

Because, if you actually read the technical details of this vulnerability, you'll know that it is a *snapd* vulnerability (which involved misconfiguration in systemd-tmpfiles). It is *NOT* a systemd vulnerability, and anyone who's telling you the opposite does not have a single idea what they're talking about.

I am specifically looking at that complete idiot on youtube who keeps bringing up things completely out of context, is a literal nazi, and whose name starts with L.

Please, don't listen to idiots who don't know anything about the subject they're bringing up.

seems this pdf is hardcoded to tell me to use a newer version of adobe reader, even if i'm not using adobe reader. incredible innovation in the pdf space

As the number of LLM-generated patches in my inbox increases, I am starting to experience the sort of maintainer stress that has long been predicted. But there's another aspect of this that has recently crossed my mind.

Just over a week ago, a new personality showed up with a whole pile of machine-generated patches claiming to fill in our memory-management documentation. A few reviewers had some sharp questions, the response to which has been ... silence. This person doesn't seem to have cared enough about that work to make an effort to get past the initial resistance.

Once upon a time, somebody who had produced many pages of MM documentation would be invested enough in that work to make at least a minimal attempt to defend it.

Kernel developers often worry that a patch submitter will not stick around to maintain the code they are trying to push upstream. Part of the gauntlet of getting kernel patches accepted can be seen as a sort of "are you serious?" test.

When somebody submits a big pile of machine-generated code, though, will they be *able* to maintain it? And will they be sufficiently invested in this code, which they didn't write and probably don't understand, to stick around and fix the inevitable problems that will arise? I rather fear not, and that does not bode well for the long-term maintainability of our software.

Stop using AI, people. I don't care if it makes things easier for you. You're sucking up water, burning the planet, models were trained on stolen data, and you're making the rich even richer. And I didn't even list all of the issues with AI.

boost this cat when they least expect it

No one is happy with age verification, in the one hand.

But in the other hand, *please* don't harass maintainers. It only makes things worse.
Don't listen to stupid people who don't know what they're talking about like lunduke.

It really does not help.

People are rightfully angry at age verification laws.

That doesn't justify any harassment campaigns towards *any* FOSS developers, maintainers nor contributors. Turn that anger towards something productive.

Get a grip people, holy shit.

The Rust project puts out an article about how they're listening to their community https://blog.rust-lang.org/2026/03/20/rust-challenges/

Except it turns out that article was drafted by an LLM https://www.reddit.com/r/rust/comments/1rz15t3/what_we_heard_about_rusts_challenges_and_how_we/obiwu24/

They claim nearly every line was rewritten by a human but I'm not sure how you could send a worse signal to your community about how much you aren't listening than having an LLM draft a post saying we're really listening, honest

Big Endian won't tell you this but you don't actually need to chose between big- and little-endian, you can just select no endianness!

Endinaness was invented by Big Endian to sell more big-endian

A new halloy release dropped! With a set of new IRCv3 features. Mainly multiline and react. And of course a bunch of other features and fixes. Really enjoying this new little client! :) https://github.com/squidowl/halloy/releases/tag/2026.5

It's funny how this phone keeps feeling faster as it gets older.

Looks like GTK is starting to get its renderer inefficiencies sorted out, as updating Flatpak runtimes has made Tuba smoother than ever 😄 #librem5

Date: Sat, 21 Mar 2026 11:59:02 -0600
From: Theo de Raadt <deraadt@openbsd.org>
To: Renaud Allard <renaud@allard.it>
cc: tech@openbsd.org
Subject: Re: [patch] ext4fs rw
In-reply-to: <2c8df0cc-938e-4036-a628-4c7f69874e0a@allard.it>

Renaud Allard <renaud@allard.it> wrote:

> Maybe it should be made clear on the website that OpenBSD will only
> allow new code made by a human. Because I feel there might be more
> requests like this and there is no point in repeating the discussion.

Yes.

#openbsd

I really appreciate folks working on Plasma Mobile though, this is really comfy (pretty much my daily-driver now)

(Yes, I still need to fix internal audio, wifi and cameras, but they’re not deal-breakers for me especially since I can use bluetooth in the meantime)

Since people keep asking, this is running on: https://wiki.postmarketos.org/wiki/Xiaomi_Mi_9_Lite_(xiaomi-pyxis)

In today's issue of "This Week in Plasma", Mr. Vader says...

https://blogs.kde.org/2026/03/21/this-week-in-plasma-time-zone-offsets-and-type-ahead-on-the-desktop/

#FreeSoftware #desktop #Plasma6 #OpenSource #RoundCorners

I would like to drop armhf (armv6) support in #AlpineLinux. The only current hardware I am aware of that is armv6 is Raspberry Pi Zero series (EOL 2030). I don't think it is worth the extra effort to support both armhf (armv6) and armv7 at this point.

Do you think we should drop armhf to free up some resources?

One thing people get wrong when considering anti-LLM policies is that they think it is unenforceable since you can't always tell if a contribution is AI-generated. This is true, but it is less about stopping any AI contribution, but warning people that if they try to sneak one in, it will be the last contribution they will ever make to the project. Its the same thing as enforcing a license. A MIT licensed project won't allow GPL contributions, but people can try sneaking them in anyways.

When impressed with postmarketOS on my PinePhone. It's been running smoothly for the past 46 days.

The state of international law.

#InternationalLaw #WorldOrder