I use this alias:

    prune-local = "!git fetch -p && for branch in $(git branch -vv | awk '/: gone]/{if ($1!=\"\*\") print $1}'); do git branch -d $branch; done"

1. Fetch the latest from my remote, removing any remote tracking branches that no longer exist

2. Enumerate local branches, selecting each that has been marked as no longer having a remote version (ignoring the current branch)

3. Delete the local branch safely

Yes. You can also continue to use SDDM.

As others have said there are challenges with the core assumption that something can similultaneously be open source and restricted from being used in AI training.

That being said, here's a repo of popular licenses that have been modified to restrict such uses: https://github.com/non-ai-licenses/non-ai-licenses

IANAL, so I can't speak to how effective or enforceable any of those are.

The sorting for the "Duration" column appears to be lexicographical, not numeric.

Agreed.

I joined a Zed hackathon at RustConf 2024 where I built the "Open in split" functionality from the file fuzzy picker. A member of the engineering team who was floating around helping folks had us exclusively work through the included collaboration features. It was a great tour of the editor, and did not feel tacked on.

There are two additional recent ones mentioned in the article:

> On Oct. 15, the Post heralded the military's push for a new generation of smaller nuclear reactors. "No 'microreactor' currently operates in the United States, but it's a worthy gamble that could provide benefits far beyond its military applications," the Post wrote in its editorial.

> A year ago, Amazon bought a stake in X-energy to develop small nuclear reactors to power its data centers. And through his own private investment fund, Bezos has a stake in a Canadian venture seeking nuclear fusion technology.

and

> Three days after the nuclear power editorial, the Post weighed in on the need for local authorities in Washington, D.C., to speed the approval of the use of self-driving cars in the nation's capital. The editorial was headlined: "Why D.C. is stalling on self-driving cars: Safety is a phony excuse for slamming the brakes on autonomous vehicles."

> Fewer than three weeks before, the Amazon-owned autonomous car company Zoox had announced D.C. was to be its next market.

Edit to respond to your edit: these are the opinion pages, not reporting.

The PSF and several other organizations that provide public package registries wrote an open letter [1] announcing a joint effort to make this situation more sustainable. I'll be interested to see where it goes.

[1]: https://openssf.org/blog/2025/09/23/open-infrastructure-is-n...

Thanks! I want to bring this up as a discussion point when I get the chance at work.

I can't find a date on this letter - is it recent?

Get your company to take the Pledge: https://opensourcepledge.com/

It says "September 23, 2025" right at the top.

The website hides the date on mobile

The date is at the top of the letter and in the url...

September 2025.

I wonder if they're mobile. Here the URL is truncated and over on openssf.org/blog they don't show the date unless you switch over to desktop view.

I'm on mobile and missed it. My bad for the spam.

The website hides the date on mobile

Works for me. Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0

From the tail end of the blog post:

> The technology that underpins this initial version of secure backups will also serve as the foundation for more secure backup options in the near future. Our future plans include letting you save a secure backup archive to the location of your choosing, alongside features that let you transfer your encrypted message history between Android, iOS, and Desktop devices.