Just absolutely no regard for security at all. None. The entire burden of self-protection shifted to humans alone at their endpoints in systems and communities entirely, foundationally built on mutual trust and trustworthiness.

@horms @lwn thanks! :)

Even Charles Darwin had bad days. Also I'll put good money that he'd have used Tumblr were he around today.

That feeling while scrolling though my morning RSS feed, and suddenly my own name appears in one of the headlines 🤩

@lwn #RSS #Linux

RE: https://fedi.lwn.net/@lwn/116161406237207111

Høiland-Jørgensen: The inner workings of TCP zero-copy

https://lwn.net/Articles/1060953/ #LWN #Linux #kernel

Last night I went to a 70th birthday party and ended up sitting next to Frank.

Frank used to work as a computer programmer, because this was the 1970s to 90s and people had normal job titles that described real things, instead of "full stack orchestration engineer" or "solutions architect".

Anyway Frank's employer was the Victorian Attorney General's department. He wrote, updated and maintained in-house software for managing the court system, trial documentation managements and so on using low level languages.

The point of this post is that there was nothing special about this period of history that made it possible for government departments to write and maintain their own software to solve their own problems then but not now.

The complete lack of any in-house capacity to do this kind of thing is a political choice. Frank is a reminder of that.

❓Have you noticed that digital products and services are getting worse? So have we!

➡️We have published a report about enshittification, on how and why digital products and services keep getting worse - and how we can turn the trend (hint: open tech, enforcement, public policy++)

Obviously @pluralistic is a big inspiration and help in this work.

More than 80 groups in Europe and the US has joined in a call to action.

More here: www.forbrukerradet.no/breakingfree

Enjoy this short film!

What if I could convince you that taking the same time to explain detailed requirements and carefully validate results with a junior colleague instead of a chatbot would not only give you two people who understood the code instead of zero, but if you do it a few times in a row you eventually get a senior colleague out of the deal for free.

KDE supports the "Keep Android Open" campaign

#Google will cut off independent developers to #Android if they do not register with Google first. This will kill independent platforms like @fdroidorg and severely impede FLOSS devs from creating apps for Android.

https://keepandroidopen.org/

Many KDE apps are deployed for Android: KDE Connect, Itinerary, Tokodon, and there's even a test version of Krita for Android.

KDE calls on Google to reverse course and @keepandroidopen.

https://keepandroidopen.org/open-letter/

@simontatham @fanf

New blog post: "The inner workings of TCP zero-copy"

Did some investigation into how exactly TCP zero-copy works under the hood, and figured I'd share my findings in a (more or less) digestible format.

https://blog.tohojo.dk/2026/02/the-inner-workings-of-tcp-zero-copy.html

#tcp #zerocopy #linux #networking

I switched to Magit last month, and just did a magit-commit-instant-fixup for the first time. Magit has completely solved the 'git problem'!

https://docs.magit.vc/magit/Editing-any-reachable-commit-and-rebasing-immediately.html

#Magit #Emacs

Not sure where #Google asked for feedback about their developer verification program, but they surely didn't talk with #FLOSS devs, civil society, privacy organisations or their #Android users

#FDroid did since September, and interacted with folks in the Fediverse, forum, email and in person

They all voiced one opinion: "developer verification must be stopped"

@marcprux has written an open letter, signed by likeminded organisations who want to #keepandroidopen

Click: https://f-droid.org/2026/02/24/open-letter-opposing-developer-verification.html

The call for papers for the eBPF'26 workshop is open: https://ebpf.github.io/2026/cfp.html. This year, the workshop will be hosted by @sospconf, the top academic conference in OS research, happening in Prague in late September! The deadline for submissions is June 19th, in just over 4 months.

Following a decision by the Codeberg e. V.'s Presidium, Codeberg e. V. has joined the ranks of many organizations as a co-signatory of the draft letter of the "Keep Android Open" initiative: https://keepandroidopen.org/draft-letter/

Apart from the impact on the many independent developers hosting their source code on https://codeberg.org, we are concerned by the greater societal implications the Android ecosystem's current trajectory will cause. For more information, see: https://keepandroidopen.org

Even as a dyslexic I can assure you I still manage to communicate just fine without using LLMs. It's literally ok. Nobody in good faith gives a fuck if something is spelled a bit wrong or with shit grammar, the message is still out there in it and if anything that makes it more human and personal anyway right?
If anything encouraging people to use LLMs to "speak correctly" opens up a whole fucking ton of worms around structural racism, classism, ableism and "learnedness"

you certainly will not regret morging continvoucly

RE: https://hachyderm.io/@thomasfuchs/116083589029041168

There’s a lot of mockery, but if I could apply (sorry, ‘morge’) my fixes retroactively before the bugs are discovered, that would be a great improvement over my current process.

Today in InfoSec Job Security News:

I was looking into an obvious ../.. vulnerability introduced into a major web framework today, and it was committed by username Claude on GitHub. Vibe coded, basically.

So I started looking through Claude commits on GitHub, there’s over 2m of them and it’s about 5% of all open source code this month.

https://github.com/search?q=author%3Aclaude&type=commits&s=author-date&o=desc

As I looked through the code I saw the same class of vulns being introduced over, and over, again - several a minute.

It's either very funny or very depressing to watch executives trip over themselves to prove who has the worst understanding of what software development actually entails.