Doesn't seem like Nate Graham AKA pointieststick, of KDE fame, has a fedi account, so I'll just share his article here myself:

https://pointieststick.com/2026/07/19/whos-responsible-for-bug-reports-on-old-software-versions/

It's a nice read, and the article about what "LTS" actually means that he links to inside the post, gets straight to the core of the issue. Nate's communication style is examplary and something to take note of.

One of the open source projects I used to (many years ago, so I am not really affected anymore) has recently decided to allow AI contributions. One of their arguments is that they judge submissions on quality, not tools used.

Back when I was an active contributor (to the project and maintainer of some other parts of the surrounding ecosystem), I got a lot of submissions that were bad.

The thing is, I absolutely loved getting these because they always came from super-enthusiastic junior people. Reviewing them and giving feedback often too much longer than implementing the feature myself. The same was usually true for the next contribution too. But that shifted over time. After a few months, I started getting patches where I didn’t find anything beyond the cosmetic that I wanted to change.

Going back further, I was one of those people when I started contributing.

Measured as code contributions over the short term, maintainers working with submitters of poor-quality PRs is a waste of time. You’re taking time away from writing code to do something that produces code more slowly.

Measured over the long term, the results are very different. Far more code in that project and closely related parts of the ecosystem has been written by people who I mentored when they came along with some bad code than by me.

It’s never a waste of my time to turn an enthusiastic and incompetent contributor into an enthusiastic and competent contributor, it’s an absolutely critical part of building a healthy project. I wouldn’t have got nearly as much out of F/OSS on a personal level if I hadn’t encountered a lot of people with the same opinion when I was one of the enthusiastic and incompetent newcomers.

But LLMs are not like that. If I spend time reviewing LLM-generated code when it would have been faster to write it myself (which, to be clear, is the case on 100% of LLM-submitted PRs I’ve seen so far), then that’s just a time sink. It’s also taking away time I could be spending helping new contributors who want to actually improve, rather than just take the review comments, feed them into an opaque system, and give me back the results.

Watercolor 0.7 - Chris McElligott

NVK Vulkan Performance Improving With Mesa 26.2 Against NVIDIA Proprietary Driver

The performance of the Nouveau kernel driver with the Mesa NVK Vulkan driver continues to improve each feature release in its quest toward better competing with NVIDIA's official Linux graphics driver with its proprietary Vulkan driver...
https://www.phoronix.com/news/NVK-Mesa-26.2-Performance

And they call it ‘progress’

I call it unnecessary destruction

When you allow AI to write your alt text.

For Instagram, my art is "Likely made with AI". Hard to be an artist in 2026...

we have macbook at home

Today the last patent for MPEG 4 Part 2 Visual finally expired.

https://meta.wikimedia.org/wiki/Have_the_patents_for_MPEG-4_Visual_expired_yet%3F

#NoSoftwarePatents #OpenCodecs #MPEG4

Hey, everybody? I get that it's frustrating when Codeberg is down. But please remember that it's a community project, and that the expectation of "everything is up 100% of the time" was created by exactly those tech companies that were killing off communities for the past 20 years. 100% uptime was never true before Facebook/Google/etc. came around, not even close.

And it's even more difficult to keep things up nowadays; there is *so much more* malicious traffic coming from the internet now than back then, especially since the rise of LLM scrapers.

So if you want Codeberg to be down less often, might I suggest reaching out to them about volunteering instead? Not right now, because they're probably pretty busy getting things back up, but once things have been stabilized a bit. Then you yourself can help improve the uptime!

#Codeberg

Who’s responsible for bug reports on old software versions?

pointieststick.com/2026/07/19/whos-responsible-for-bug-reports-on-old-software-versions

Consider this hypothetical: An operating system (OS) ships version 1.5 of a piece of software. Meanwhile, the latest version of that software is 3.0. A user on that OS experiences an issue in version 1.5, or has an idea for a new feature. Who should they…

Today I got compared to RMS, what a world: https://scalie.zone/@aks/116857138145245913

Just to make it clear, I do not eat my own toe skin.

Yes, I blocked them now, I am just bit saddened by this whole thread. I did not expect someone more "prominent" like that just outright start trolling.

Step 1: Tell Claude to rewrite a project in Rust for literally no reason
Step 2: Tell Claude to write a post about it because you no longer know how to
Step 3: Bask in the glory of the achievement

It’s so hard to turn off Apple Intelligence with macOS 27 and iOS 27.

You can’t turn off Apple Intelligence with one switch. You can turn off “reply suggestions” on macOS, but not on iOS. Things you type with “smart event details” turned on (default) in Calendar may not make it into the event.

I used to be able to create a new event, and typing would match against prior events. A past event named identically would inherit the same time. Now, it doesn’t!

Now that’s what I call “intelligence”!

For some reason the entirety of kernel releases got nuked from cdn.kernel.org?

https://cdn.kernel.org/pub/linux/kernel used to host kernel release tarballs. Now it's a 404.

Someone emailed helpdesk@kernel.org and they said they're resyncing, but does anyone know what happened there?

LoongArch Pi Zero, absolute cinema

Had a user come into #nouveau today, because colors were oversaturated, very bright green (using Mate)

A bit back and forth, and we found it was the TV switching to a "vivid" color profile

As a thank you, they told a little story:

Back in the days they were working in a TV shop and there was this customer complaining about a "green tint" on their home cinema system. Customer brought it back into the store. Tried with a demo DvD, perfect colors. Turns out, the customer was watching the matrix

continuing the trend of changing the header background on floppy.cd-rom.net once per month, here’s the edit I made for July:)