@ariadne all the time. I run sway and I don't want to use the Alt key.

@TheEvilSkeleton Yeah I'm not saying the packager is right. But it helps to restate the context even if you think the packager might already be aware, it can clear up things and that packager may also be working on a million other things besides gnome-calendar.

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.

@TheEvilSkeleton so I got linked to this before ... from what I can tell in the issue, as an outsider, it looks like neither side wanted a productive conversation, and it just felt rude on both sides. The issue body itself also initially didn't look completely clear what the actual problem is, it just asked for rebranding everything without any specific reason.
This article itself is just inflammatory, again pointing fingers at LM which is not helpful.

Note linuxmint is not innocent either, they definitely messed up by packaging gnome-calendar in this state, but I feel if the discussion started by clearly stating the problem (people reporting long solved bugs in the wrong place, which is hurting upstream) and not pointing fingers all the time the outcome probably would've changed significantly.

But instead there was a lot of miscommunication, both from your side and their side, miscommunication that could have definitely been avoided, which is sad to see.

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

@thomholwerda How come I have like 50-ish firefox tabs open and another 20-ish librewolf tabs open and I can still use jitsi just fine? 8 GB of RAM, Alpine Linux, sway...

I'd say it is a Windows problem too, nowadays windows happily takes 2-3 GB of RAM on idle.

And they call it ‘progress’

I call it unnecessary destruction

When you allow AI to write your alt text.

@Andres4NY @TheEvilSkeleton well it is on mint for not redirecting the user to the correct bug tracker (theirs, downstream)

@TheEvilSkeleton There's this blog post also which I think quite resonates with how I think about this whole situation: https://pointieststick.com/2026/07/19/whos-responsible-for-bug-reports-on-old-software-versions/

@TheEvilSkeleton so I got linked to this before ... from what I can tell in the issue, as an outsider, it looks like neither side wanted a productive conversation, and it just felt rude on both sides. The issue body itself also initially didn't look completely clear what the actual problem is, it just asked for rebranding everything without any specific reason.
This article itself is just inflammatory, again pointing fingers at LM which is not helpful.

Note linuxmint is not innocent either, they definitely messed up by packaging gnome-calendar in this state, but I feel if the discussion started by clearly stating the problem (people reporting long solved bugs in the wrong place, which is hurting upstream) and not pointing fingers all the time the outcome probably would've changed significantly.

But instead there was a lot of miscommunication, both from your side and their side, miscommunication that could have definitely been avoided, which is sad to see.

@me @davidrevoy yep, reminds me of this gem

@davidrevoy Meta AI detects that human art is made by AI... so funny

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

@hexaheximal no need to overthink them

we have macbook at home