I don't know what's more stupid: #OpenSSH using different authentication flow depending on whether you have a `.pub` file in addition to the private key or not, or #GitHub suddenly starting to reject one of the two valid RFC 4252 workflows.

https://thorsell.io/2026/07/21/github-ssh-keys.html

#SSH

An average two-feeted European hearing Americans talk about all their tall feet: 🤯.

Let's get this straight: anything created with "AI" is #slop.

It doesn't have to be vibe-coded. It doesn't have to be horrible code. It doesn't matter that you've spent hours perfecting the prompt. It doesn't matter that ten people have spent a week reviewing it in detail.

As long as an "AI" took part in writing it, it's slop. It's an unethical technology, and anything created with it is tainted. It's an inhuman technology, and you're supporting it. You're being disrespectful to your users and contributors. You're putting your own convenience over humanity. You're aiding the worst murderous assholes in the history of humanity. And what's perhaps worst, you quite likely believe that you are making a net positive contribution, that you're helping people, while you're actually disrespecting and harming them.

#NoAI #NoLLM

The state of #Python ecosystem right now: almost everything is slop. Some projects are complete vibe-coded slop (autobahn, chardet, cryptography). Some projects are disguised slop ("Coding agents shouldn't co-author themselves.")

There is only a handful of human projects left (Flask being one bright example). And they're being killed. They're being killed by the neverending slew of slop pull requests. They're being killed by all their dependencies becoming slop. They're being killed because this whole ecosystem has became such a complete cesspit that you have zero motivation to do anything.

EDIT: and honestly, this is only going to get worse. When you kill the incentive to work on projects, you only get more slop. Maintainers give in, and more projects become slop. Or they give up, and projects get forked unto slop.

#NoAI #NoLLM

Which of the displays do you identify with? 🔥

#Wrocław Leśnica station building.

#rail

And the next big blocker for #Python 3.15 in #Gentoo is time-machine. Which is obviously broken. There's a patch but it's #slop and complex, and it's sitting for 3 months already with no reply. Because obviously patching CPython internals is so much a better idea than freezegun ever were. All these time-based tests need all the ricing you can get; portability doesn't matter.

https://github.com/adamchainz/time-machine/pull/618

Dependency cooldowns are a nice idea, but I dare say they're a short-term solution.

They resemble the idea of avoiding poison by waiting for someone else to start eating first. That works, provided that someone actually eats first, and that the poison works fast. But eventually it leads to that awkward silence at the table when nobody wants to risk the first bite.

Adapting dependency cooldowns means basically waiting for "someone else" to notice the problem. At some point when large enough number of projects adapts them, we're going back to square one — except with an artificial few-day delay.

#security #FreeSoftware

So to remove someone from repository's ACL on #GitHub, I need to click the trash icon next to their name. Is it just me, or is that symbolic troubling?

New on #blog: pkgbump: from a dumb tool to an irreplaceable helper

https://blogs.gentoo.org/mgorny/2026/06/21/pkgbump-from-a-dumb-tool-to-an-irreplaceable-helper/

"""
Bumping packages is one of the most common tasks of a #Gentoo developer. It shouldn’t then be surprising that it is the one most asking for some kind of automation, and that the #pkgbump script would be one of the first scripts to become a part of the mgorny-dev-scripts package.

Today’s pkgbump have come a long way from the trivial script of its first iteration. The most recent versions finally feature the feature I desired for a long time: version manipulation. This also made it possible for the script to become a complete version bumping tool rather than just a part of a larger workflow. In this post, I’d like to shortly tell the story behind the changes, and demonstrate the new options.
"""

#packaging

Some people think that #LLM usage costs rising will start undoing some of the harm caused by the #AI hype. I don't think that's really going to help that much.

I'm not even talking about all the projects that were ensloppified and enshittified already. I'm not talking about all the technical debt. I'm not talking about all the forks that will have to be maintained forever. I'm not talking of all the projects that were abandoned because of burnout, or because they were only hype-oriented. And I'm not talking about all the corporations that will continue submitting slop.

I'm talking about the loss of trust. After all, we're not talking of people who realized they were wrong and are sorry. We're not talking of people realizing that it was wrong to forfeit ethics and morals in the name of "productivity". We're talking of people who are jumping ships because their previous approach turned out not to be profitable anymore. We're talking of gamblers who left the casino because they went broke. They aren't sorry that they gambled; they are sorry that they've lost. And they'd be happy to do it again at the nearest opportunity.

So, I'm sorry to say, but #FreeSoftware is never going to be the same again. A lot of people have shown their true colors, and I won't forget that.

#NoAI #NoLLM #OpenSource #FLOSS