Sunday, 28 June

17:28

Link [Scripting News]

To read scripting.com you need a browser that supports HTTP.

Link [Scripting News]

Why email newsletters made sense. Email has no character limits, can represent bold and italic, links, titles, enclosures, basically most features of the web, and social media places limits on what writers can write. That's where the literate social web went, and the bloggers too. Like how birds are really dinosaurs.

14:28

Link [Scripting News]

If you're working on a social web app that supports inbound and outbound RSS, I'd like to help, so our products can interop beautifully. That's the reason I'm doing this work, to establish a baseline for interop in the social web. RSS is the obvious candidate. If we didn't have it, we'd have to invent it. I'd much prefer doing the work openly, so if you can, write a post and send me a link. I think it's time for us to go back to the way we built network systems before Google and the VCs took over. Put up an app and see who works with it. My email address is on the About page on my blog.

Link [Scripting News]

Programming tip. If your app has globals, create an object called globals, and put all of them in there. Someday you may want to swap in one set of globals for another, this makes it easy.

11:07

That CO alarm is giving me a headache [RevK®'s ramblings]

OK, yes that is an old joke, but I do have a slight mystery over the CO alarm.

This first happened last year, and drove me round the bend. A chirp every 49 seconds. This is normally a smoke alarm with low battery.

The problem is that we have 8 alarms in the house, and trying to work out which is chirping is not as easy as it sounds, especially when it is 2am, as it always is with these tings.

I actually ended up replacing every battery and still had a chirp. I then remembered there is a smoke alarm in the loft, and replaced that, only then to realise it was the CO alarm  in the loft! I went to replace that and found it is mains only, and Ei3018 CO alarm. Annoyingly it continued to chirp for some time once removed from the power.

I actually ended up buying a new one, and has been fine for over a year.

Then this week, it happens again. Thankfully I remember the loft this time. What is extra odd is that when I opened the loft hatch, the chirping stopped!

The next night it started again and did not stop. So I removed it, and waited. I put back in place next day.

The next night it started again, so removed, and new one ordered.

But I decided to actually read the manual, and it is odd.

It did not alarm!

Now, a key thing here is, it did not alarm. I would know, I have been in the house all the time, it is linked to all the other alarms, and to a relay input to my alarm/monitoring system as well. It did not do an alarm, honest.

But the manual says it has a memory mode, where, for 24 hours after an alarm, it will chirp. There is however a problem with this.

  1. It had not alarmed!
  2. It stopped chirping when I opened the loft hatch, so was clearly not doing a 24 hour chirp.
  3. It is a single chirp - the manual explains it does 2 or 3 chirps, etc, for different types of alarm.

However, reading further, the manual does have a single chirp every 48 seconds. This is for "AC mains off or low battery backup", or (with green LED) low battery backup. I do not think it had an LED on.

So it does indeed sounds like the backup battery is depleted and the action is "replace alarm".

But this is just over a year for a device that should last over 10 years, arrrg!

I wonder why?

10:14

The generic headline and the lazy slogan [Seth's Blog]

If you can swap your slogan with a competitor’s without changing the meaning of either brand, then your slogan is meaningless.

For example, “You belong here” is not a positioning statement for a college seeking new students. It’s just noise.

It also doesn’t help to mix weasel words with more weasel words and then add specifics. On charity’s pitch: “Your contribution can help up to 35 people.”

“Up to” covers a lot of ground, doesn’t it?

It’s true that the copy we use can be noisy decoration, not often read or fully understood. But that doesn’t mean we shouldn’t put in the effort to make it useful and powerful.

07:14

Russell Coker: Plaud [Planet Debian]

While watching a YouTube video I saw an advert for the Plaud AI Note Taker [1]. The Plaud device looks pretty good for what it does, taking notes and managing them, using some sort of LLM function to manage the notes. The devices all cost about $300 which is an amount that doesn’t seem unreasonable for someone who’s in a lot of meetings. One of the models is the “NotePin” that seems comparable to the Humane AI Pin I previously blogged about [2].

The business model for Plaud is based on only allowing 5 hours per month of free transcriptions, then charging $16.25/month for 20 hours per month and $33.33/month for unlimited use. That’s quite expensive for any serious use.

The number of people in the market for an audio recording system that automatically transcribes things may be greater than the number of people in the market for all the stuff that the Humane AI Pin did, but it still may not be enough to run a profitable business when competing with apps on mobile phones.

While the product does look decent it seems that they are making the same mistakes as the original Humane developers did, of wanting to lock it down as a subscription based service which reduces the usability of the device. If they had sold an Android hand-held computer with their own app pre-loaded and allowed the user to install a different app then it would have been much more usable. If they had sold Android devices designed for the note taking market and allowed people to choose their own apps to install then their products would have a much longer life expectancy.

The majority of Android devices in use are probably out of support but still working while the Humane AI pin can’t be used any more and at some time in the not too distant future the Plaud devices will also become unusable. People who buy devices like the Plaud seem to be unaware of the history of such things and the expected future for them. But possibly some people just consider $300 for a year of use to be an acceptable price. If someone wanted to purchase a new high end phone every year and sell their previous one they would probably have a net cost of about $500/year.

Maybe I should look for work with a company with an implausible AI based business plan. It would be fun developing such a device if you weren’t emotionally invested in the project. Just develop new technology, earn a heap of money, play with fun computers, and move on to the next thing when it collapses. Just like all the Internet companies about 25 years ago.

Russell Coker: Some GPU Stuff [Planet Debian]

After getting a HP Z4 G4 tower server/workstation to house my Intel Battlemage GPU [1] I’ve been playing around with some GPU stuff. For years I’ve been just buying GPUs based on the resolution and price and not bothering about anything else due to lack of ability to measure what cards are doing. The nvidia-smi program is really good for NVidia/CUDA setups but I hadn’t been aware of anything similar for AMD cards. As I prefer AMD cards for my workstations due to driver issues with NVidia that was a problem for me.

I’ve recently discovered that the program nvtop (Debian package nvtop) shows the GPU use of multiple GPU types, for me it’s worked on AMD and Intel discrete GPUs and shows some information on Intel integrated GPUs, I don’t have others convenient for testing at the moment. Currently BOINC has the Einstein@Home [2] project running on the HP Z4 G4 and it’s using between 66% and 100% of GPU compute power and 1.6G of GPU RAM. Using 100% GPU compute power allegedly takes 62W of power out of the 190W quoted TDP. I presume that the power use reported by nvtop is very inaccurate.

A friend installed a LLM on that system and the libraries used for the LLM were sufficient that BOINC just started using the GPU.

On my workstation running an AMD “[Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X]” (actually R560) with 4G of GPU RAM I have mpv taking 1G of GPU RAM to play a FullHD video expanded to a full screen window on my 5120*2160 display. I also have about 2G used by the kwin_wayland process (the Wayland server for KDE). That doesn’t leave enough GPU RAM to allow Einstein@Home to use the GPU. When playing the FullHD video in question (which is 1.2G for 42 minutes – about 500KB/s) at 1.5* speed (a common playback speed I use) that takes about 30% of the compute power on my GPU.

I had installed the rocm-opencl-icd package on my workstation (with a 5120*2160 monitor) and restarted boinc-client.service which is all that’s needed to allow BOINC to use an AMD GPU. Then the screen started flickering as the Einstein process repeatedly core dumped which I initially assumed to be it’s reaction to not having enough GPU RAM available. On every core dump the screen flickered so it went through a process of dozens of screen flickers until it had caused a sufficient number of core dumps and BOINC gave up running that job.

Another annoyance is that the boincmgr program (the graphical program for managing BOINC systems) launches two webkit processes that each use about 400M of GPU RAM, so even if other things weren’t using all my GPU RAM the boincmgr process would stop the BOINC jobs from using the GPU. I shut down some of the programs that were using GPU RAM until there was 2G free and the BOINC process kept crashing so it seems that there is some other issue.

On another system with a 4K monitor there were Chrome and Chromium GPU process taking 1.1G and 500M of GPU RAM respectively and the KWin Wayland process was taking 1G of GPU RAM. So that’s well over half the GPU RAM for just browsers and Wayland. With programs like Kitty (terminal emulator) and Nheko (Matrix client) taking over 100M of GPU RAM it seems that 4G is the bare minimum for GPU RAM with modern software and a 4K or similar display.

I also noticed the kscreenlocker_greet process taking 440M of GPU RAM. I wonder if a hostile web server could make a web browser take more GPU RAM and starve the screenlocker of GPU RAM, could that allow forcing a screen lock operation to fail?

It seems that 4G is the minimum for modern systems, which isn’t necessarily a problem as GPUs that are capable of driving 4K displays tend to have no less than 4G. My local computer store has new GPUs with 4G starting at $120 but 12G seems to be the next option up which starts at about $400.

Ebay currently has a selection of AMD GPUs with 8G of RAM under $200. I’ve had some problems with the GPU in my workstation crashing as described in my previous post where I thought it was driver issues [3]. I now believe that there are hardware issues and will look into buying one of the cards with 8G.

Further Investigation

I need to determine which of the AMD GPUs that are currently going cheap on ebay are best. While my current PC has support for 150W PCIe power I’d rather something less power hungry than that. I have occasional issues of mpv reporting that my system is too slow for a video so slightly more compute power on the GPU would be good, but I think that every available option has significantly more compute power.

I need to find out what the relationship is between screen resolution and GPU memory. If I get an 8K display or an array of 4*4K displays (which is quite plausible as 27″ 4K displays go for $230 each) will I find 16G of GPU RAM as limiting as I find 4G now?

The nvtop program tracks PCIe data transfers for AMD GPUs, I haven’t yet seen more than 25MB/s and I need to do more tests to see what the maximum is. Running on an Intel Battlemage card nvtop doesn’t report PCIe data transfer speed which is a missing feature in either the driver or the program. I need to find out where the problem is and report a bug if someone hasn’t already done so.

The GPU RAM use of some applications seems excessive. 440M for a lockscreen? 100M+ for a terminal emulator? 320M for Thunderbird?

Saturday, 27 June

23:28

Steve McIntyre: It's dead, Jim! [Planet Debian]

I previously wrote about the upcoming UEFI CA rollover. Well, it's happened now - the old Microsoft UEFI CA from 2011 expired yesterday:

Third Party Marketplace Root (used for signing option ROMs and other software)

  Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation UEFI CA 2011
  Validity
    Not Before: Jun 27 21:22:45 2011 GMT
    Not After : Jun 27 21:32:45 2026 GMT

It's dead - it's not coming back...

The world doesn't seem to have ended yesterday, so I guess we did ok? :-)

How did we do?

After a lot of prodding behind the scenes, Debian and many other distributions managed to get new shim binaries dual-signed with both the old and new CAs. The members of the shim-review team did a sterling job with reviews in the last few weeks. Since I started pushing people in May, we've had 21 reviews accepted successfully - see here for the list. Great stuff! Microsoft have also been working quickly - many of those shim submissions were accepted and signed by Microsoft very quickly too, with a turnaround time of less than 1 day in some cases.

Not all of those signed shims have been published and used by the distros involved yet, but expect to see them in the wild in the coming weeks and months.

These binaries should be good for people to use for the foreseeable future, until either we need to do another CA rollover or (sadly, more likely) we find an issue in shim that necessitates a new release.

What's next?

We already have one of our new dual-signed shim binaries in place in Debian, in unstable and testing (Forky) right now. In a couple of weeks from now, we'll be rolling out very similar new dual-signed shim binaries in the next point releases for Debian 12 (bookworm) and Debian 13 (trixie). We'll also be upgrading fwupd in both those point releases, to make DB and KEK updates work better.

For more information about these updates, see https://wiki.debian.org/SecureBoot/CAChanges. For your own safety, validate that your systems are updated when possible. If you don't, they may fail to boot in future.

18:49

Link [Scripting News]

Claude can understand code no human could. Ever, under any circumstances. Just like a compiler can understand any code we throw at it. Way beyond what code obfuscation tools can do.

17:21

Link [Scripting News]

In our work we have arrived at the point where we read and study a piece I published in 1997, but was written in 1988 or so. Esp the part about LBBS. It's a really good thing I wrote that because I forgot how it worked, but reading that it all comes back. We're going to go far beyond where Twitter went with reading message structures on the web. I had already done a lot of the work in the 80s.

Link [Scripting News]

The other day Matt joked about how old I am, in public, and I am pretty old. But Matt, I was paying attention then as I am now, and connecting the dots. No one else working today, I'd venture, knows what it's like to create and run a modem-based dial-up Twitter-like system on an Apple II with a 10MB Corvus hard drive. Yet it worked, and people loved it. If you weren't alive in 1981, you wouldn't know anything about this. I remember talking with Doug Engelbart when I was running UserLand. If you don't know who he is, look him up. He blazed a trail we were turning into a highway, and we're all using his inventions all the time. Every chance I got to sit down with him I did. I wanted him to work with us, to critique everything we were doing. He had a lot of knowledge that disappeared when he passed on a few years later. That's the sad thing, at my advanced age, that I am trying to avoid. And btw, as surprise, Claude really understands this stuff. I've never seen anything like it with a human, and I've worked with some great humans.

17:14

Jonathan McDowell: onak 0.6.5 released [Planet Debian]

I had intended that the next release of onak, my OpenPGP keyserver, would be 0.7.0, and include OpenPGP v6 support (RFC9580). However events conspired to make a 0.6.5 release a really good idea.

Firstly, I threw an LLM at the code base and asked it to review it. This isn’t intended to be a post about LLMs, but there’s a considerable amount of pressure at work to be “AI native”. I’m very much an “AI” sceptic, so I figured throwing it at a code base I know well might be an interesting exercise. It did find a bunch of embarrassing mistakes, but I don’t think there was anything earth shattering that a human reviewer wouldn’t have pulled me on. The problem is with a hobby project with a single user there’s no actual review of my work.

I also enabled GitHub’s security scanning. It mostly complained about format strings, and those were easy enough to fix up.

Next I threw AFLplusplus at the code. I’d previously tried American Fuzzy Lop, but not in some time. AFL++ found a whole bunch of places I should really have checked available buffer lengths and wasn’t doing so. It really is an incredibly easy tool to get up and running.

valgrind is also a tool I’ve used before, and rate highly. Thankfully it didn’t find anything in my testing this time.

Finally I threw a few more automated tests into the mix and discovered something has changed around dynamic linking such that the libonak symbols in the dynamic key database backends were using private copies, rather than the main binary. This caused problems with seeing the correct configuration settings in some instances.

All in all this release is not my proudest moment; a bunch of the issues fixed should never have made it to a release.

(Also, just to explicitly state it, all the actual code in this release was artisanly crafted by me, in vim. The only involvement of an LLM was for a review pass.)

Available locally or via GitHub.

0.6.5 - 27th June 2026

  • Lots of fixes/improvements around length checking
  • Added extra basic tests for maxpaths/sixdegrees/CGI
  • Correctly end transactions in the stacked backend
  • Ensure the file backend avoids stale key data on updates
  • Fix decoding of v2/3 signature creation times
  • Fix EdDSA signature parsing when r < 249 bits long
  • Fix migration of bools from old to new config style
  • Fix parsing of new config details for DB parameters
  • Fix problems with linking + dynamic backends
  • Fix RSA-SHA2-384 signature checking
  • Fix sixdegrees parsing of keyids with high bit set
  • Handle failures in maxpath more gracefully
  • Make new style config path match old path

16:21

View From a Hotel Window 6/27/26: Chicago [Whatever]

There is a parking lot in this picture, but it’s over in the corner, and I think it’s attached to the marina. The rest is convention center and Lake Michigan.

Also, hello, Chicago! It is good to be in you again. I am here for the American Library Association event, and I regret to say that unless you’re attending you’re not likely to see much of me. Never fear, I will return. I always do.

— JS

15:21

Three stable kernel updates [LWN.net]

The 7.1.2, 7.0.14, and 6.18.37 stable kernel updates have been released; each contains a relatively small number of important fixes. Note that 7.0.14 is the end of the 7.0.x series.

13:07

GNU Parallel 20260622 ('Rape Gang Inquiry') released [stable] [Planet GNU]

GNU Parallel 20260622 ('Rape Gang Inquiry') has been released. It is available for download at: lbry://@GnuParallel:4

Quote of the month:

  GNU Parallel is much nicer than xargs and more powerful ... definitely recommended!
    -- boomertsfx@reddit

New in this release:

  • testsuite reorganized.
  • Bug fixes and man page updates.


GNU Parallel - For people who live life in the parallel lane.

If you like GNU Parallel record a video testimonial: Say who you are, what you use GNU Parallel for, how it helps you, and what you like most about it. Include a command that uses GNU Parallel if you feel like it.


About GNU Parallel


GNU Parallel is a shell tool for executing jobs in parallel using one or more computers. A job can be a single command or a small script that has to be run for each of the lines in the input. The typical input is a list of files, a list of hosts, a list of users, a list of URLs, or a list of tables. A job can also be a command that reads from a pipe. GNU Parallel can then split the input and pipe it into commands in parallel.

If you use xargs and tee today you will find GNU Parallel very easy to use as GNU Parallel is written to have the same options as xargs. If you write loops in shell, you will find GNU Parallel may be able to replace most of the loops and make them run faster by running several jobs in parallel. GNU Parallel can even replace nested loops.

GNU Parallel makes sure output from the commands is the same output as you would get had you run the commands sequentially. This makes it possible to use output from GNU Parallel as input for other programs.

For example you can run this to convert all jpeg files into png and gif files and have a progress bar:

  parallel --bar convert {1} {1.}.{2} ::: *.jpg ::: png gif

Or you can generate big, medium, and small thumbnails of all jpeg files in sub dirs:

  find . -name '*.jpg' |
    parallel convert -geometry {2} {1} {1//}/thumb{2}_{1/} :::: - ::: 50 100 200

You can find more about GNU Parallel at: http://www.gnu ... rg/s/parallel/

You can install GNU Parallel in just 10 seconds with:

    $ (wget -O - pi.dk/3 || lynx -source pi.dk/3 || curl pi.dk/3/ || \
       fetch -o - http://pi.dk/3 ) > install.sh
    $ sha1sum install.sh | grep c555f616391c6f7c28bf938044f4ec50
    12345678 c555f616 391c6f7c 28bf9380 44f4ec50
    $ md5sum install.sh | grep 707275363428aa9e9a136b9a7296dfe4
    70727536 3428aa9e 9a136b9a 7296dfe4
    $ sha512sum install.sh | grep b24bfe249695e0236f6bc7de85828fe1f08f4259
    83320d89 f56698ec 77454856 895edc3e aa16feab 2757966e 5092ef2d 661b8b45
    b24bfe24 9695e023 6f6bc7de 85828fe1 f08f4259 6ce5480a 5e1571b2 8b722f21
    $ bash install.sh

Watch the intro video on http://www.youtub ... L284C9FF2488BC6D1

Walk through the tutorial (man parallel_tutorial). Your command line will love you for it.

When using programs that use GNU Parallel to process data for publication please cite:

O. Tange (2018): GNU Parallel 2018, March 2018, https://doi.org/1 ... 81/zenodo.1146014.

If you like GNU Parallel:

  • Give a demo at your local user group/team/colleagues
  • Post the intro videos on Reddit/Diaspora*/forums/blogs/ Identi.ca/Google+/Twitter/Facebook/Linkedin/mailing lists
  • Get the merchandise https://gnuparall ... igns/gnu-parallel
  • Request or write a review for your favourite blog or magazine
  • Request or build a package for your favourite distribution (if it is not already there)
  • Invite me for your next conference


If you use programs that use GNU Parallel for research:

  • Please cite GNU Parallel in you publications (use --citation)


If GNU Parallel saves you money:



About GNU SQL


GNU sql aims to give a simple, unified interface for accessing databases through all the different databases' command line clients. So far the focus has been on giving a common way to specify login information (protocol, username, password, hostname, and port number), size (database and table size), and running queries.

The database is addressed using a DBURL. If commands are left out you will get that database's interactive shell.

When using GNU SQL for a publication please cite:

O. Tange (2011): GNU SQL - A Command Line Tool for Accessing Different Databases Using DBURLs, ;login: The USENIX Magazine, April 2011:29-32.


About GNU Niceload


GNU niceload slows down a program when the computer load average (or other system activity) is above a certain limit. When the limit is reached the program will be suspended for some time. If the limit is a soft limit the program will be allowed to run for short amounts of time before being suspended again. If the limit is a hard limit the program will only be allowed to run when the system is below the limit.

12:56

Pluralistic: Zuckerberg's increasingly bizarre war on whistleblowers (27 Jun 2026) [Pluralistic: Daily links from Cory Doctorow]

->->->->->->->->->->->->->->->->->->->->->->->->->->->->-> Top Sources: None -->

Today's links

  • Zuckerberg's increasingly bizarre war on whistleblowers: Under no circumstances should you rush out and read the book that prompted Mark Zuckerberg to demand $111m and eternal auctorial silence.
  • Hey look at this: Delights to delectate.
  • Object permanence: Flame warriors; Cryptography and casinos; TSA v dying 95 year old woman's adult diaper; Neoliberalism and Brexit; Beyond solutionism; How Thiel cheated with his Roth; Inequality's stabilizer; Palm Pilot school; Gillmor on PR flacks; "How I Edited an Agricultural Paper; Conservative judge chokes liberal judge; Hollywoodnomics; Rubber fingertips v fingerprint readers; Snowden's telepresence robot; "Shrill"; Moral hazard, "Three Rocks."
  • Upcoming appearances: London, Edinburgh, Sydney, Melbourne, Brighton, London, South Bend.
  • Recent appearances: Where I've been.
  • Latest books: You keep readin' em, I'll keep writin' 'em.
  • Upcoming books: Like I said, I'll keep writin' 'em.
  • Colophon: All the rest.



Four female chorousters in sumptuous Renaissance robes. Each one's mouth has been stopped up by a Facebook 'thumbs up' icon. Behind them looms Mark Zuckerberg's grinning Metaverse avatar. The book they are reading from has flooded their faces with light. In the background is a sky full of ominous blue/red clouds.

Zuckerberg's increasingly bizarre war on whistleblowers (permalink)

More than a decade ago, a group of young, internet-connected Belarusian dissidents launched a series of increasingly high-stakes, increasingly surreal confrontations with the corrupt, authoritarian government of Alexander Lukashenka, a man who is often called "the last Soviet dictator."

Lukashenka's secret police – still called the KGB – routinely terrorize and kidnap pro-democracy activists, and all forms of protest are banned. It was against the backdrop of this unrelenting oppression that the activists launched a series of whimsical "flash mobs" that challenged the Lukashenka regime's willingness to crack down on even the most innocuous behavior.

One of these flash mobs was an ice cream social: activists converged on a public square to eat ice cream cones. Lukashenka's thugs beat them and dragged them away:

https://web.archive.org/web/20070609164305/http://pics.livejournal.com/litota_/gallery/0000bcch

The protestors thought that by daring Lukashenka to arrest people for eating ice cream, they could create a win-win situation: either Lukashenka would be revealed as the kind of asshole who thinks it should be illegal to eat ice cream, or he'd be revealed as the kind of weakling who couldn't keep a lid on dissent.

Lukashenka took the bait. And took it. And took it. In the years that followed, protesters would be arrested for smiling, clapping, and just standing silently:

https://www.indexoncensorship.org/2011/07/belarus-protesters-rally-on-the-web/

The world learned that Lukashenka was a buffoon, and Belarusians affirmed their view that this buffoon would not hesitate to mete out the most vicious punishments for the most innocuous actions:

https://sci-hub.st/10.1080/25739638.2021.1928880

Speaking of thin-skinned, paranoid, wildly corrupt buffoons who will stop at nothing to silence their enemies, how about that Mark Zuckerberg, huh? Sure, all the headlines these days are about Zuck's intention to transform Facebook into a sports betting site:

https://www.businessinsider.com/metas-zuckerberg-enters-the-prediction-market-arena-polymarket-2026-6

But in the UK, Zuckerberg's war on whistleblowers keeps finding new, ice cream grade depths of absurdity to plumb. The whistleblower in question is, of course, Sarah Wynn-Williams, author of the internationally bestselling memoir Careless People, which details the criminality she witnesses during her years as the head of Facebook's international relations team:

https://pluralistic.net/2025/04/23/zuckerstreisand/#zdgaf

Careless People is full of revelations about the gross institutional misconduct of Facebook, including its knowing encouragement of a genocide in Myanmar. But it's also full of stories about the severe personal failings of Facebook's executive team, especially Sheryl Sandberg, Joel Kaplan and Mark Zuckerberg.

These three come off as the most colossal of assholes, cruel, petty and predatory. Sandberg comes across as a sexual abuser who dreams of trafficking in poor people's organs. Kaplan is an oaf whose plan to provide paid internet access to refugee camps falls apart once he learns that refugees in camps don't have any money (he also takes points off of Wynn-Williams' workplace evaluation for being "unresponsive" over a period when she was in a near-death coma). Worst of all, though, is Zuckerberg, whose sins range from cheating at Settlers of Catan to endangering the Colombian peace process after a 50-year civil war because he refused to get out of bed before noon. Zuck is also revealed to have given the Chinese state access to all of Facebook and the power to censor content they disliked, as part of a failed bid to get permission to offer a Facebook service in China.

It's a terrible company, with awful products, run by the worst people. Wynn-Williams' conditions of employment required her to sign a contract that bound her to silence (nondisclosure), forbade her from speaking ill of the company (nondisparagement), and denied her access to the legal system in all her dealings with Meta (binding arbitration).

Together, these three clauses – routinely used by Meta to silence would-be whistleblowers – meant that after Wynn-Williams's book was published, Meta got its arbitrator – a lawyer who is paid by Meta to adjudicate contractual disputes instead of an actual judge – to order her to never promote or even speak about her book.

The arbitrator awarded Meta $50,000 for each criticism that Wynn-Williams levied, quickly coming to a total of over $11,000,000. This vastly exceeds the assets and lifetime earning potential of Wynn-Williams and her husband (a reporter with the Financial Times). If this bill ever truly comes due, they will be wiped out.

Which raises an interesting question: what else can they do to her? Once they've secured civil damages that exceeds her net worth several times over, why shouldn't she just flout her agreement? "Freedom's just another word for nothing left to lose," and all that.

Nevertheless, Wynn-Williams has scrupulously hewed to the arbitrator's rules, steadfastly remaining silent about her book, its contents, and her experiences at Facebook/Meta. When she and I appeared onstage together in London for the launch for my book Enshittification last year, she fell silent and assumed a blank expression any time the subject of Meta came up, and she didn't sign or sell books afterward:

https://www.barbican.org.uk/whats-on/2025/event/cory-doctorow-with-sarah-wynn-williams-chris-morris

When she won the British Book Award, she did not speak to accept it, and the cover of her book was blurred out on the overhead screen (she gave an acceptance speech on behalf of her co-winner, the late Virginia Giuffre, who was abused by Jeffrey Epstein and who accused Prince Andrew of sexual assault):

https://www.theguardian.com/books/2026/may/11/sarah-wynn-williams-and-virginia-giuffre-jointly-win-freedom-to-publish-prize-at-british-book-awards

Nevertheless, when she was booked to speak – about a subject other than her book – at the Hay Festival on a stage with Tim Wu and Carole Cadwalladr, Meta sent a legal threat to the festival and Wynn-Williams, claiming that if by speaking about anything in public, she would violate the arbitrator's order. Accordingly, Wynn-Williams maintained total silence and a blank facial expression for an hour on stage, saying not one word, while Wu and Cadwalladr carried on a discussion. Careless People was withdrawn from the festival bookshop on the days she appeared there:

https://www.theguardian.com/technology/2026/may/31/meta-legal-action-forces-facebook-whistleblower-to-stay-silent-at-hay-festival

Nevertheless, Meta has informed Wynn-Williams that her silent, motionless appearance on a stage constitutes a further breach of her "agreement" and that they are going to seek even more damages from her. This act of anti-ice cream thuggery has pushed Wynn-Williams over the edge and now she's sued to invalidate her contract:

https://www.theguardian.com/technology/2026/jun/25/whistleblower-sarah-wynn-williams-sues-meta-attempts-to-silence-her-careless-people

Her lawyers have posted their documents related to the suit, including a 285-page declaration by Wynn-Williams explaining the great lengths she's gone to in order to comply with Meta's demands, and the company's absolute intransigence and arbitrary menace:

https://katzbanks.com/sarah-wynn-williams-meta-lawsuit-documents/

Why would Meta be so intent on destroying this one high-profile whistleblower? Surely they've heard of the Streisand Effect. There is no better way to ensure that Wynn-Williams' book (already a NYT #1 bestseller) continues to attract readers than to continue to escalate these threats.

I think they're perfectly aware that they are convincing more people to read Careless People (you should read it, it's genuinely excellent):

https://us.macmillan.com/books/9781250391230/carelesspeople/

But I think they've decided that this is a price worth paying, because:

a) They've done even worse things since Wynn-Williams parted ways with the company; and

b) They're laying off thousands of workers because their giant bet on AI has been a flop, leaving them with a massive cash crunch; and

c) By destroying Sarah Wynn-Williams, they can terrorize all those thousands of bitter ex-employees into silence about the even graver sins the company has committed.

That's my theory, anyway:

https://www.businessinsider.com/meta-layoffs-managers-software-engineers-ai-spending-2026-6

Lukashenka knew that arresting children for eating ice cream would make him a laughingstock abroad. Zuckerberg knows that threatening Wynn-Williams for standing in wooden silence on a stage makes him look like history's most guillotineable billionaire. But both Lukashenka and Zuckerberg are willing to be thought a thin-skinned bully, so long as that means the people they oppress the most are too terrified to ever challenge their authority.


Hey look at this (permalink)



A shelf of leatherbound history books with a gilt-stamped series title, 'The World's Famous Events.'

Object permanence (permalink)

#25yrsago Actual music piracy https://www.theguardian.com/uk/2001/jun/13/ukcrime.nickhopkins

#25yrsago Flame warriors https://web.archive.org/web/20010603044914/http://www.winternet.com/~mikelr/flame1.html

#25yrsago World court says Arizona murdered German prisoners by denying them consular access https://www.cnn.com/2001/WORLD/europe/06/27/germany.court/index.html

#25yrsago Private school buys every student a Palm Pilot https://web.archive.org/web/20010709075203/https://www.wired.com/news/school/0,1383,44812,00.html

#25yrsago Dan Gillmor’s guide for PR flacks https://web.archive.org/web/20010626230530/http://web.siliconvalley.com/content/sv/2001/02/20/opinion/dgillmor/weblog/PR.htm

#20yrsago German publisher attacks Bulgarian books-for-blind site https://web.archive.org/web/20060629065445/https://protest.bloghub.org/2006/06/27/fight-for-copyrights-in-bulgaria-turns-ugly/

#20yrsago Photographer calls critic’s boss to complain https://www.flickr.com/photos/thomashawk/176785431/

#20yrsago Daddle: a kid-sized saddle for adults https://web.archive.org/web/20060618012713/https://www.cashelcompany.com/dad.php

#20yrsago More on cryptography and online casinos https://memex.craphound.com/2006/06/26/more-on-crypto-and-online-casinos/

#20yrsago Reasons that HD DVD formats have already failed https://www.audioholics.com/editorials/10-reasons-why-high-definition-dvd-formats-have-already-failed

#15yrsago Undercover video from North Korea: starving children, hungry soldiers https://web.archive.org/web/20110629182200/http://www.abc.net.au/news/stories/2011/06/27/3253979.htm

#15yrsago TSA asked 95 year old woman in a wheelchair in terminal stage of leukemia to remove adult diaper for pat-down https://web.archive.org/web/20110627091434/http://www.nwfdailynews.com/news/mother-41324-search-adult.html

#15yrsago Reading of Mark Twain’s “How I Edited an Agricultural Paper” https://ia801406.us.archive.org/22/items/Cory_Doctorow_Podcast_209/Cory_Doctorow_Podcast_209_Mark_Twain_Editing_an_Agricultural_Paper-fixed.mp3

#15yrsago Paramount sends copyright notice to Shapeways user over 3D printable Super 8 cube https://toddblatt.blogspot.com/2011/06/cease-and-desist.html

#15yrsago Advice Goddess: How much longer must we be subjected to invasive TSA patdowns? https://www.advicegoddess.com/archives/2011/06/24/i_think_youre_c.html

#15yrsago Conservative Wisconsin Supreme Court Justice alleged to have choked liberal colleague https://talkingpointsmemo.com/muckraker/wis-justice-ann-walsh-bradley-justice-prosser-put-his-hands-around-my-neck-in-anger-in-a-chokehold

#15yrsago Hollywoodonomics: how Harry Potter and The Order of the Phoenix “lost” $167M https://deadline.com/2010/07/studio-shame-even-harry-potter-pic-loses-money-because-of-warner-bros-phony-baloney-accounting-51886/

#10yrsago I’m profiled in the Globe and Mail Report on Business magazine https://web.archive.org/web/20160628142940/https://www.theglobeandmail.com/report-on-business/rob-magazine/the-crusader-fighting-lock-happy-entertainment-conglomerates/article30520282/

#10yrsago Rubber fingertips to use with fingerprint-based authentication systems https://www.csmonitor.com/World/Passcode/Security-culture/2016/0627/Fake-fingerprints-The-latest-tactic-for-protecting-privacy

#10yrsago How I grilled the best steaks I’ve ever eaten https://memex.craphound.com/2016/06/27/how-i-grilled-the-best-steaks-ive-ever-eaten/

#10yrsago Supreme Court strikes down Texas abortion law https://www.nbcnews.com/news/us-news/supreme-court-strikes-down-strict-abortion-law-n583001?cid=sm_tw

#10yrsago Snowden’s flesh is trapped in Russia, but his mind roams the world in a robot body https://nymag.com/intelligencer/2016/06/edward-snowden-life-as-a-robot.html

#10yrsago China’s $10B/year PR ministry mired in political fight with anti-corruption/loyalty enforcers https://web.archive.org/web/20160701235749/http://www.economist.com/news/china/21701169-xi-jinping-sends-his-spin-doctors-spinning-who-draws-party-line?fsrc=scn/tw/te/pe/ed/whodrawsthepartyline

#10yrsago Snowden publicly condemns Russia’s proposed surveillance law https://www.theguardian.com/world/2016/jun/26/russia-passes-big-brother-anti-terror-laws

#10yrsago Yes Men punk the NRA with “buy one gun, give one gun” program https://www.youtube.com/watch?v=Ikb66V2rDcw

#10yrsago Shrill: Lindy West’s amazing, laugh-aloud memoir about fatness, abortion, trolls and rape-jokes https://memex.craphound.com/2016/06/27/shrill-lindy-wests-amazing-laugh-aloud-memoir-about-fatness-abortion-trolls-and-rape-jokes/

#10yrsago Neoliberalism, Brexit (and Bernie) https://crookedtimber.org/2016/06/26/tribalism-trumps-neoliberalism/

#10yrsago McDonald’s 1987 fashion catalog is a horrorshow https://www.flickr.com/photos/jasonliebigstuff/3050116620/

#10yrsago Beyond “solutionism”: what role can technology play in solving deep social problems https://ethanzuckerman.com/2016/06/22/the-worst-thing-i-read-this-year-and-what-it-taught-me-or-can-we-design-sociotechnical-systems-that-dont-suck/

#10yrsago Donald Trump’s annotated Walk of Fame star https://dduane.tumblr.com/post/146444083461/someome-spray-painted-the-mute-sign-on-donald

#5yrsago New York City's 100 worst landlords https://pluralistic.net/2021/06/26/wax-rothful/#nyc-landlords

#5yrsago How Peter Thiel gamed the Roth IRA for tax-free billions https://pluralistic.net/2021/06/26/wax-rothful/#thiels-gambit

#5yrsago The Overlapping Infrastructure of Urban Surveillance https://pluralistic.net/2021/06/26/wax-rothful/#surveillance-infographic

#5yrsago The Doctrine of Moral Hazard https://pluralistic.net/2021/06/27/the-doctrine-of-moral-hazard/

#1yrago Bill Griffith's 'Three Rocks' https://pluralistic.net/2025/06/27/the-snapper/#9-to-107-spikes

#1yrago Surveillance is inequality's stabilizer https://pluralistic.net/2025/06/26/autostabilizer/#slicey-bois


Upcoming appearances (permalink)

A photo of me onstage, giving a speech, pounding the podium.



A screenshot of me at my desk, doing a livecast.

Recent appearances (permalink)



A grid of my books with Will Stahle covers..

Latest books (permalink)



A cardboard book box with the Macmillan logo.

Upcoming books (permalink)

  • "The Post-American Internet," a geopolitical sequel of sorts to Enshittification, Farrar, Straus and Giroux, 2027
  • "Unauthorized Bread": a middle-grades graphic novel adapted from my novella about refugees, toasters and DRM, FirstSecond, April 20, 2027

  • "Enshittification, Why Everything Suddenly Got Worse and What to Do About It" (the graphic novel), Firstsecond, 2027

  • "The Memex Method," Farrar, Straus, Giroux, 2027



Colophon (permalink)

Today's top sources:

Currently writing: "The Post-American Internet," a sequel to "Enshittification," about the better world the rest of us get to have now that Trump has torched America. Fourth draft completed. Submitted to editor.

  • A Little Brother short story about DIY insulin PLANNING

This work – excluding any serialized fiction – is licensed under a Creative Commons Attribution 4.0 license. That means you can use it any way you like, including commercially, provided that you attribute it to me, Cory Doctorow, and include a link to pluralistic.net.

https://creativecommons.org/licenses/by/4.0/

Quotations and images are not included in this license; they are included either under a limitation or exception to copyright, or on the basis of a separate license. Please exercise caution.


How to get Pluralistic:

Blog (no ads, tracking, or data-collection):

Pluralistic.net

Newsletter (no ads, tracking, or data-collection):

https://pluralistic.net/plura-list

Mastodon (no ads, tracking, or data-collection):

https://mamot.fr/@pluralistic

Bluesky (no ads, possible tracking and data-collection):

https://bsky.app/profile/doctorow.pluralistic.net

Medium (no ads, paywalled):

https://doctorow.medium.com/

Tumblr (mass-scale, unrestricted, third-party surveillance and advertising):

https://mostlysignssomeportents.tumblr.com/tagged/pluralistic

"When life gives you SARS, you make sarsaparilla" -Joey "Accordion Guy" DeVilla

READ CAREFULLY: By reading this, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

ISSN: 3066-764X

10:49

Seeking a complement [Seth's Blog]

One of the nicest thing you can do for someone you care about is point them to an idea, a book, a talk or a tool that will amplify their work and help them get to where they’re going.

It’s not easy. It means you understand their goals, see them for who they are and care enough about their work to amplify it.

That’s why filling in the missing piece with a complement is worth much more than an empty platitude or compliment.

08:42

Microsoft capitulates again, extends Windows 10 support by another year [OSnews]

It’s been quiet for a few days since I’ve been sick, but I’m feeling a bit better since today marks the official end of my one month of using Windows 11 that you people donated for. An article about my experience is definitely upcoming, including whether or not I’ll actually stick with Windows 11 on my laptop or go back to Linux, but before we get there, let’s talk about Microsoft once again capitulating to the reality that a lot of people really don’t want to let go of Windows 10.

In a surprising move, Microsoft has quietly confirmed that it’s extending Windows 10 support until October 12, 2027, which is one full year beyond the October 2026 cutoff that home users had been planning around.

↫ Abhijith M B at Windows Latest

Hundreds of millions of people are still using Windows 10, and with the “AI” techbros buying up all the RAM and other chips for their pachinko machines – making this whole thing a bit of an own goal for prime “AI” booster Microsoft – buying new PCs that are actually compatible with Windows 11 isn’t exactly a fun prospect for the vast majority of us normal folk dealing with the cost-of-living crisis. As such, Microsoft really doesn’t have any other choice but to keep extending support for Windows 10. It ain’t much, but I’ll take any morsel of justice I can get.

While everyone else has to pay for getting access to these Windows 10 updates, users in the European Union get them entirely for free thanks to the Digital Markets Act. This additional year, too, can be partially attributed to the DMA, as the very same consumer rights organisations who pressured Microsoft into giving EU users truly free access to the Extended Security Updates also put pressure on the company to offer these for more than just one year.

Basic consumer protection legislation works.

05:49

Anti-Muslim hate and antisemitism [Richard Stallman's Political Notes]

*Anti-Muslim hate and antisemitism are twin crises. We must confront them together.*

As usual, the religion that is really dangerous in the west is the majority religion here — Christianity. Particularly the evangelical variety.

Cuts to intervention programs [Richard Stallman's Political Notes]

*[The saboteur's] cuts to intervention programs could increase violent crime, experts say. Community programs are more effective at reducing violence than simply making arrests, advocates say.*

Meta suing former employee [Richard Stallman's Political Notes]

Meta is suing a former employee, Sarah Wynn-Williams, for publishing a book about her experiences working there.

She was invited to panel at a major book festival, but because the court had threatened to fine her, she dared not speak or make any gestures.

The book is called Careless People. If you want to buy the book, or any book, I urge you not to obtain it from Amazon. By paying cash for it anonymously, you can fight against Orwellian surveillance.

I have found a local bookstore that is willing to let me order books anonymously, paying cash in advance, and I occasionally do that. That enables me to order new books (but not used books) that are not available in a physical book store. Since the store does not know my name, I think its request for cash in advance is entirely reasonable.

Maybe you too can find a bookstore near you that will do this for you.

European web site published identities of deportation thugs [Richard Stallman's Political Notes]

A European web site and its volunteer contributors help defend democracy in the US by publishing the identities of masked, badge less deportation thugs.

Why bully directs systematized cruelty [Richard Stallman's Political Notes]

Why does the bully direct his agents to perform so much systematized cruelty on randomly chosen victims? One possible explanation is that imposing an inflexible system manipulates people to believe that the system is justified and correct.

Why UK banned Hasan Piker and Cenk Uygur from speaking [Richard Stallman's Political Notes]

Why did the UK ban Hasan Piker and Cenk Uygur from speaking at Oxford? Arwa Mahdawi's response is, "Because on Gaza, we punish the witness, not the crime."

*Banning leftwing activists from entering Britain: an illiberal move with a long history in [Britain].*

The Oxford Union invited them to speak by videoconference instead.

I hope they don't plan to use Zoom, because Zoom censors remote talks about political topics much as the UK government censors presencial ones.

Deportation prison for families [Richard Stallman's Political Notes]

The deportation thugs were planning to set up a special deportation prison specifically for families.

It might be a little less cruel to children than an ordinary deportation prison, normally used only to jail adults. However, if it tortures the prisoners like most US deportation prisons, it could do irreparable harm in a few weeks.

Palantir on path for access to UK medical records [Richard Stallman's Political Notes]

The UK is on a path to give Palantir access to patients' medical records in England. If Palantir gets that, it will let the magats use it for persecution.

Jamaican thug accused of shooting protester [Richard Stallman's Political Notes]

A Jamaican thug is accused of shooting a protester dead. The protest was over the fatal shooting of her cousin by another thug a few days before.

House passes resolution to end US fighting with Iran [Richard Stallman's Political Notes]

The House of Representatives passed the resolution to end US fighting with Iran. The Senate has not yet voted, but it may pass.

As the article shows, the bullshitter has already demonstrated how he would respond if the resolution does pass: with falsification. His philosophy is, "Grab what you want, then state contemptuous bullshit as an excuse."

If senators don't like to be given bullshit, they will need to start blocking lots of other things the bullshitter wants.

Iran and US both losing the war [Richard Stallman's Political Notes]

*Iran and the US both think they are winning the war. The truth is they are both losing.*

Prisoners denied food and water until they sign documents [Richard Stallman's Political Notes]

Prisoners of the deportation thugs report they are denied food and clean water unless they sign documents they can't even read.

The attempt to force false confessions is a standard practice of cruel governments that despise justice. Many countries have done it. It is the shame of the US to be one of them.

Biofuel "solution" can do terrible harm [Richard Stallman's Political Notes]

The biofuel "solution" to global heating can do terrible harm if it substitutes for increased solar and wind electric generation. *Experts say increased use of crops for fuel is "dangerous game" that could send food price inflation soaring.*

Pretend Intelligence agents mess things up like Mr Magoo [Richard Stallman's Political Notes]

Because Pretend Intelligence "agents" do not really understand what they were told to do, not at the level of ground truth that is, nor the actual effects of their actions, they often mess things up like Mr Magoo.

Impeachment to induce splits in the Republican Party [Richard Stallman's Political Notes]

Ralph Nader argues that an impeachment drive against the corrupter now, before the 2026 election, would be a good way to induce splits in the Republican Party and may be drive him to resign.

His arguments may be valid, but I wonder how much less destructive and cruel Vance would be.

Dangers of storing data with tech companies [Richard Stallman's Political Notes]

One of the dangers of tech companies storing your personal data, and personal data about you, in their online dis-services is that agents of repression can copy that data from the company without even informing you.

Plan to break up National Center for Atmospheric Research [Richard Stallman's Political Notes]

The wrecker's henchmen plan to break up and wreck the National Center for Atmospheric Research, stating global heating denialism as their motive.

A court blocked one attack, ruling that it was "arbitrary and capricious".

If they succeed, the blow to climate modeling may indirectly kill millions more people, perhaps hundreds of millions more, but it will be hard to estimate how many of additional deaths were due to the sabotage of NCAR. In 20 years or so, their successors will deny that the saboteurs of today had anything to do with the world-wide disasters, but people who reject their lies will understand who is responsible.

Scott Pelley told to mis-report about Renee Good [Richard Stallman's Political Notes]

Scott Pelley reports that Bari Weiss, appointed saboteur of CBS News, told the 60 Minutes team to say that Renee Good was "driving toward" the thug that shot her. (Their video showed she was steering to avoid him.)

She also directed the team to make the protesters appear more violent (another request for a lie).

FBI fired analyst who warned of "Catholic violent extremists [Richard Stallman's Political Notes]

The FBI fired just recently the analyst who warned in 2023 of potential danger from "Catholic violent extremists" opposed to abortion.

As we all know, the danger from anti-abortion activists in the US comes mainly from evangelicals, not from Catholics. And their violence is primarily lawfare rather than direct violence.

Aside from those details, the warning was right on track. State efforts to ban abortion have killed a number of women who needed an abortion to save their lives after a complication in pregnancy.

I suppose the reason that the FBI fired them is that the violent anti-abortion extremists are supporters of the saboteur in chief, who is the boss of the head of the FBI.

US was moving towards oligarchy before corrupter [Richard Stallman's Political Notes]

Robert Reich argues that the US was steadily moving towards oligarchy before the corrupter pushed it quickly to the extreme.

Therefore, if we do overcome the corrupter and his followers, they may turn out to have taught us a crucial lesson about defending democracy, justice, and honesty.

Claims UK cops treat white suspects worse than non-white suspects [Richard Stallman's Political Notes]

Right-wing extremists in the UK constantly accuse the cops of treating white suspects worse than nonwhite suspects, with no evidence except how often they claim this.

Meanwhile, statistics continue to show bias against black suspects.

It is a standard right-wing extremist strategy: claim the opposite of the truth, and repeat it in a chorus until people lose track of what is true.

Cuban journalist forced into exile [Richard Stallman's Political Notes]

A Cuban journalist founded an independent internet magazine. "State security" forced him into exile by showing him on TV labeled as a "CIA agent".

Sweeping vision for planetary survival [Richard Stallman's Political Notes]

* Humanity can raise living standards, reduce inequality and keep global heating within a 2°C rise, according to a sweeping vision for planetary survival.*

The plan includes redistributing a large part of rich people's wealth. I don't have the time or background to validate the details, but it sounds plausible, if we can overcome the power of the rich.

The authors of the plan describe it.

It is worth a try, since our current course is taking us to disaster.

Millions paid by US to countries to receive deportees [Richard Stallman's Political Notes]

The US has paid millions to convince various countries to receive deportees from the US who have no relationship from those countries.

80% of them were re-deported from there to their home countries. (Most of them, the US could not deport to their home countries because they were in danger of persecution there.)

Amazingly, the US plans to deport 400 Iranians to Iran, *including Christian converts, ethnic minorities, and political dissidents.* The persecutor isn't satisfied with torturing and killing people directly; he wants to help Iran do so too.

04:49

Russ Allbery: Review: The Folded Sky [Planet Debian]

Review: The Folded Sky, by Elizabeth Bear

Series: White Space #3
Publisher: Saga Press
Copyright: June 2025
ISBN: 1-6680-7812-0
Format: Kindle
Pages: 483

The Folded Sky is a far-future space opera and a fairly direct sequel to Ancestral Night, but with a different protagonist. You do not need to have a vivid memory of the previous book to read this one. It is somewhere around Elizabeth Bear's 31st (!) novel, depending on how one counts and what one includes.

Sunyata Song is an archinformist, which is sort of an archaeologist, sort of a librarian, and sort of a historian. She recovers, decodes, and organizes information so that it can be preserved and made usefully available. As the book opens, she is, after an exceedingly long white space journey in an actively hostile ship with a (to Sunya at least) an atavistically off-putting crew, reaching her goal: a vast artifact that I won't describe further to avoid any spoilers for Ancestral Night. She is eager to get to work, an eagerness that is both heightened and made more anxious by the discovery that her academic rival and abusive ex has arrived before her. The pirate attack doesn't help, nor (at least at first) does the surprise appearance of her wife and kids.

The opening of this book is a lot of infodumping mixed with nearly stream-of-consciousness emotional dumping. The style shift in this series continues to surprise me; previously, Elizabeth Bear books avoided reader hand-holding to the point of bafflement if you weren't paying close attention. Not here. The Folded Sky takes the shift perhaps too far, and I almost stalled out at the start of this book when Sunya's near-constant self-conscious litany and analysis of fears and concerns started feeling like whining.

The book picks up considerably after the attempted murder.

About a third of the way through, The Folded Sky feels like it's settling into a recognizable subgenre of murder mystery except set in the far future with fascinating technology and aliens. There has been an attempted murder on a closed station besieged by pirates. There is a law enforcement officer present, but they don't have a lot of investigative experience. For various reasons, Sunya decides to start poking around while being conscious she has no idea what she's doing. The bumbling detective is a common trope, so I thought that was where the story was headed.

It is, sort of. There is a mystery and Sunya is involved in solving it. But that's only a small fraction of what's going on, and by the end of the book the plot has shifted firmly back to the genre of space opera, with a side note of family... drama is the wrong word. Whatever one would call a story about raising a rebellious teenager while trying very hard to not turn conflicts into actual drama.

I am fascinated by the characterization of this book. Sunya is something of an emotional mess, but Bear doesn't use that fact in the ways that I would normally expect. Similar to Ancestral Night, I finished this book thinking that Folded Space is primarily an examination of rightminding, but a more subtle one than the previous novel.

Rightminding is a central technology of the White Space series, and I suspect its intended thematic core. Humans in this civilization are equipped with near-universal implants that allow conscious manipulation of one's neurotransmitters and thus emotional state, either by the wearer or by a helpful nearby AI. The fox, the implant used to accomplish this, comes with some other features such as sensory recordings and the ability to load ayatanas (James White–style personality recordings to provide some bit of necessary expertise), but rightminding is its primary and most frequently-used function. It is the critical technology that allowed humans to break out of cycles of endless war and join the other peaceful inhabitants of the galaxy in a shared civilization.

The name is (intentionally, I assume) Orwellian because Bear knows that many readers, particularly those from the US who have been steeped in simplistic libertarian ideas, will find the idea profoundly creepy. (This was a major plot point in Grail.) This book is not the argument for the technology, though; Bear dealt with that in Ancestral Night. This book is a look at its practical messiness for a person who needs a lot of psychological support.

Sunya is anxious, prone to catastrophizing, hates surprises, has some PTSD-style symptoms around space habitats due to earlier trauma, and is also dealing with the unwelcome reappearance of her ex-girlfriend who stole her work. Her first-person narration tends towards insecurity and anxiety spirals, and in another book this might signal an unreliable narrator. In this book, though, there are no dramatic emotional revelations or backstory twists the way there were in Ancestral Night, and the resolution of her troubled relationship with her daughter only partly hinges on plot developments. Instead, Sunya muddles through, with a lot of self-analysis, help from her fox, and a great deal of support from her wife.

This makes it sounds like the emotional mess at the start of the book is left unresolved at the end, but that's not true at all. The muddling through works! Sunya keeps doing things that I thought were foreshadowing some catastrophe, but she knows herself better than the reader does. Bear largely avoids the sudden ruptures that are normally used to resolve emotional problems in fiction. Instead, Sunya spends a lot of time and energy working on her thinking and her relationships while trying to be ethical and useful, and those efforts slowly bear fruit.

I'm worried this makes the book sound boring; rest assured that it isn't. This emotional subplot is only an undercurrent in the novel, and the main plot has enough weird science, alien aliens, and space opera drama to satisfy my page-turning desires.

I'm focusing on the emotional arc in this review because I find it so unusual and so oddly compelling, particularly in retrospect. This is not how one normally does emotional development in a novel. Sunya's fox and rightminding aren't even the focus except when the pirates express their typical libertarian disgust for the idea. Rightminding is an entirely normal part of Sunya's life that she relies on. It doesn't solve all of her problems, but it gives her a foundation from which to tackle them in the slow and frustrating and inconsistent way that is required outside of novels, via a long series of small decisions to be the person she wants to be.

I think The Folded Sky will be more hit and miss for readers than the other books of this series. Sunya was, for me at least, a much harder character to like early in the book, and it takes quite a while for the plot to get going. But this is one of those books that I've not stopped thinking about since I finished it. I think it makes a fascinating pair with Ancestral Night. The first book makes the philosophical argument for rightminding, and this book shows the practical reality with all of its messiness. The Synarche has some significant flaws (including the status of AIs, which is another interesting subplot), but it's a workable system.

It feels rare to read a science fiction novel that shows this level of messiness without pairing it with an argument for radical change, and as frustrating as it was to read in places, I am intrigued by the overall effect. Sometimes acknowledging problems and working on them within an existing framework works.

Followed by a book tentatively titled Shipwreck Star that does not yet have a release date.

Rating: 7 out of 10

00:56

The case of the DLL that was not present in memory despite not being formally unloaded, part 2 [The Old New Thing]

Last time, we looked at crashes caused by a DLL being removed from memory behind everybody’s back, causing crashes when somebody tried to call into that no-longer-there DLL that everybody thought was still there.

A colleague of mine who was looking at other crashes coming from this process found that most of those other crashes were also of the form “a data structure was corrupted because somebody wrote the single byte 01 into it.” That piece of information made everything fall into place for my side of the investigation.

We saw earlier that the bottom bit of the HMODULE is set for datafile module handles. Therefore, if one of these stray 01 bytes happens to overwrite the bottom byte of an existing HMODULE handle, that turns it into a (fake) datafile module handle. And then, during process destruction, a component dutifully cleans up the DLLs they loaded by freeing them (say because they were stored in an RAII type like wil::unique_hmodule), the code will pass this (fake) datafile module handle to Free­Library. The Free­Library function sees the bottom bit set and says, “Oh, this must be the handle to a module that was loaded via LOAD_LIBRARY_AS_DATAFILE,” so it frees it as a datafile.

Freeing a datafile module means undoing the steps that were taken when the module was loaded as a datafile: Unmapping the DLL from memory. In particular, loading a module as a datafile does not add the DLL to the list of DLLs that were loaded as code; therefore, unloading a datafile module doesn’t remove it from that list. As far as the DLL list is concerned, the DLL is still in memory.

A one-bit error caused the code to lie and attempt to free a module handle that did not correspond to a Load­Library call, resulting in mass havoc.

The “DLL unmapped from memory” crash is just an alternate manifestation of the “somebody is writing 01 bytes to places they shouldn’t” bug. The original bug had a larger bucket spray than we initially thought.

The good news is that all of the crashes have funneled down to a single bug. The bad news is that you now have to debug this one memory corruption bug.

Unfortunately, at the time of this writing, the root memory corruption bug in the third party program has yet to be identified. We don’t know whether it’s coming from an operating system component or from the program itself. Though the fact that it appears to occur only in one process, where it sprays across multiple modules, suggests that it’s a problem with that program, or that there’s something peculiar about how this specific process uses the system.

If you look at the original stack trace, you can see that the problem is occurring at process termination. That’s probably why the problem has lurked for so long: Crashes at exit often go unnoticed because there is no end-user loss of functionality. The user was finished with the program anyway. Whether it exits cleanly or with a crash doesn’t affect the user much.

Sorry. Not all stories have a happy ending.

The post The case of the DLL that was not present in memory despite not being formally unloaded, part 2 appeared first on The Old New Thing.

Jonathan Wiltshire: Streamlining Debian Updates with AI: The Stable Update Adviser [Planet Debian]

Please consider supporting my work in Debian and elsewhere through Liberapay.


Some months ago I started working on a small experiment: a specialised LLM assistant for Debian maintainers preparing proposed updates for stable and oldstable.

The aim is not to replace review by the Stable Release Managers, nor to automate away maintainer judgement. It is meant to be a pre-advice tool: something maintainers can use while they are still preparing a proposed update, before sending it to other people to review.

If you’ve uploaded to stable before you may have some experience with our acceptance criteria. Does the version sort correctly? Is the changelog clear enough? Is the delta focused? Are the patches documented? Are the right bugs or CVEs mentioned? Are they of sufficient severity? What is the risk to users of stable? Is there an ABI change hiding in the diff?

These are the sort of checks where a structured first pass can be useful, provided it is treated as advice rather than authority.

To explain what the tool does, what could be more appropriate in an AI age than to ask it?

Describe yourself and your abilities and limitations for a blog post.

It answers:

I’m Debian Stable Update Adviser, a specialised ChatGPT assistant for Debian maintainers preparing proposed updates for Debian stable and oldstable.

My main job is to review a single .debdiff and give practical, policy-aware feedback before a maintainer submits or uploads a proposed update. I focus on whether the update appears suitable for Debian stable or oldstable, especially under the Stable Release Managers’ expectations for minimal, targeted, low-risk changes.

I can inspect a debdiff for Debian changelog quality, including suite, version, bug references, CVE mentions, and rationale. I can check version correctness using Debian dpkg version semantics. I can review packaging changes under debian/, such as patches, maintscripts, symbols files, conffiles, Build-Depends, autopkgtests, and control metadata. I can also group upstream source changes into behavioural and non-behavioural categories, and flag areas that may carry regression risk.

My reports are intended to be concise and useful to maintainers. A typical review includes a quick summary, behavioural and non-behavioural change breakdown, mechanical policy checks, risk assessment, stable-policy checklist, acceptance likelihood, rationale, maintainer advice, and a clear conclusion.

My limitations are important. I cannot prove that a package builds, that tests pass, that the bug is fully fixed, or that the Stable Release Managers will accept the upload. I also do not replace maintainer judgment, archive review, autopkgtest results, reproducibility checks, or real-world upgrade testing. I can only review the provided debdiff and point out likely issues, risks, and improvements.

I also do not proceed without a valid debdiff. The whole point of my review is to assess the actual proposed delta, not to speculate from package names or bug descriptions alone.

In short, I act as a focused pre-review assistant for Debian stable and oldstable proposed updates: useful for catching policy, versioning, changelog, packaging, and regression-risk issues early, but not a substitute for the Debian review process itself.

That last point is an important one. This is not an oracle, and it is not part of the Debian archive machinery. It is a checklist with some language-model assistance, aimed at reading a debdiff and pointing out things that might be worth another look.

I know that commercial AI and LLM tools are not universally welcome in Debian. That is understandable. Debian depends on transparency, human responsibility, licensing clarity, and technical correctness. LLMs have obvious problems in all of those areas. They can be wrong, and worse, they can be wrong in a fluent and plausible way. They are impossible to reproduce and their training is opaque.

But I see this as a useful first pass for a maintainer who is unused to working in stable, and would benefit from a virtual mentor giving their proposal a quick check and reassurance. Perhaps they don’t have a more experienced co-maintainer to ask. Perhaps they are conscious that stable reviews are presently a two-man effort and want to avoid adding round trips to that load. Perhaps they just need some reassurance.

So despite my reservations I am today opening the adviser up for general use, and I’m interested in feedback about how it responds to real world proposals in various states. Most of the examples I have tested with already had a green light, so the value added by the adviser is limited. I would especially be interested in seeing a transcript alongside the submitted debdiff.

Try it out

I would dearly love to build this in a more Debian-ish environment, but for now I’m limited in resources and skill to do that (help is welcome). Until that’s a reality, you can try out the ChatGPT implementation: Debian Stable Update Adviser

Friday, 26 June

22:42

The Chinese Control the Majority of Argentina’s Squid Fleet [Schneier on Security]

Chinese companies control nearly two-thirds of Argentina’s own squid fleet.

21:00

19:56

Imperium Maledictum [Penny Arcade]

The primary way I interact with Warhammer these days is through fiction and videogames - which I'm sure works just fine for them. New versions of the flagship game, Warhammer 40,000, come out fairly frequently I would say - and with them comes a host of rule changes, changes for how armies are constructed, and changes to what your models do - up to and including exile. 11th Edition just came out, and I've looked at it and looked at it; you can look at it too. I wonder who outgrew who; the conservative rule shifts and terror of their own fanbase makes the game feel inert. And it's gotten so expensive that I'm considering going elsewhere for rules and printing my own models out of poison.

19:07

[$] Reports from OSPM 2026, day three [LWN.net]

The Power Management and Scheduling in the Linux Kernel Summit, which still goes by the historical acronym OSPM, was held in Cambridge, UK, in mid-April. As has become traditional, the presenters at that event have since written summaries of their sessions, and this work has kindly been made available to LWN for publication. The third day's sessions covered a wide range of topics, including GPU affinity, profile-guided scheduling, paravirtualization scheduling, quality of service, and more.

18:28

Urgent: US Postal Service delivery [Richard Stallman's Political Notes]

US citizens: call on the US Postal Service to continue delivering to anyone.

See the instructions for how to sign this letter campaign without running any nonfree JavaScript code--not trivial, but not hard.

Urgent: Make billionaires and trillionaires pay their fair share [Richard Stallman's Political Notes]

US citizens: call on your congresscritter and senators to make billionaires and trillionaires pay their fair share.

See the instructions for how to sign this letter campaign without running any nonfree JavaScript code--not trivial, but not hard.

US citizens: Join with this campaign to address this issue.

To phone your congresscritter about this, the main switchboard is +1-202-224-3121.

Please spread the word.

Urgent: Reject Jay Clayton as director of national intelligence [Richard Stallman's Political Notes]

US citizens: call on the Senate to reject Jay Clayton as director of national intelligence. He is loyal to the corrupter rather than to the country he ought to serve, and that makes him unfit.

US citizens: Join with this campaign to address this issue.

To phone your congresscritter about this, the main switchboard is +1-202-224-3121.

Please spread the word.

Block demand for voting list [Richard Stallman's Political Notes]

US citizens: call on Congress to block the bully's threat-backed demand for the complete voting list of each state.

US citizens: Join with this campaign to address this issue.

To phone your congresscritter about this, the main switchboard is +1-202-224-3121.

Please spread the word.

18:21

Agentic Code Review [Radar]

The following article originally appeared on Addy Osmani’s blog site and is being republished here with the author’s permission.

Coding agents are extraordinarily good now, and getting better fast. The interesting consequence is that the hard part of engineering moved from writing code to deciding whether to trust it, which makes review the most leveraged skill in software right now. How you approach it depends enormously on who you are: A solo developer with no users and a team maintaining a 10-year-old application are not solving the same problem.

I am more optimistic about agentic engineering than I have ever been. The agents are genuinely good, they get better every month, and on an ordinary day I now ship things I would not have attempted a year ago. This write-up is a map of where the interesting work went, because it did move, and most teams have not fully caught up to where.

Code review used to work because of a happy accident of relative speed. A senior engineer could read code faster than a junior could write it, so review kept pace without anyone designing it to, and the team absorbed how the system fit together as a side effect of reading each other’s diffs. A lot of that was not deliberate. It fell out of a single fact: Writing code was the slow, expensive part, and reading it was cheap and fast.

That fact no longer holds. An agent will produce a thousand lines of often solid, well-formatted code in less time than it takes me to read this paragraph, while a human’s reading speed has not changed since roughly the day we started staring at screens for a living. So the constraint moved downstream, to the one step that did not get faster: a person being confident the change is right. I don’t think that’s a loss. It’s the most leveraged place in software to be good right now, and it’s where I’ve put most of my attention this year.

There’s a happy twist here that shapes the rest of this piece. The same tools generating all that extra code are also the best thing I have for keeping up with it. On my own projects, including the popular open source ones, I now point Claude Code or Codex at a batch of incoming PRs and have them triage the queue for me, and that has genuinely changed how I spend my time. So this is not an anti-AI argument, and I will come back to exactly how I use AI.

It’s also not a data dump, and not another round of whether letting a model write your code is wonderful or the end of the craft, because that framing is useless. The only answer that survives contact with a real codebase is that it depends entirely on who you are. A developer vibe-coding a side project only a dozen people will ever run and a team keeping a 10-year-old enterprise system alive for another quarter share almost no constraints worth naming, and most of the advice in circulation is really one of those two people telling the other how to live.

What the 2026 data actually shows

The productivity gains from AI are real, but raw output overstates them: about four times the code for a tenth more delivered value. The gap between those numbers is review work, which is exactly why review is where the leverage now sits.

For a couple of years this was an anecdotal argument. It’s now measured at scale, by organizations with no shared agenda and in several cases competing commercial interests, and the measurements keep pointing the same way: AI pushes output sharply up and pushes both quality and reviewability down.

Faros AI instrumented 22,000 developers across 4,000 teams and tracked what happened as teams moved from low to high AI adoption. This is March 2026 data, about as current as anything here. The upside is real. Developers merge considerably more PRs and complete more work and throughput per engineer climbs. Then the rest of the report:

  • Code churn is up 861%.
  • The incidents-to-PR ratio is up 242.7%.
  • The per-developer defect rate is up from 9% to 54%.
  • Median review duration is up 441.5%, with time to first review and average review time both roughly doubling.
  • PRs merged with zero review are up 31.3%.

The last figure is the one I find hardest to dismiss, because nobody chose to stop reviewing. Reviewers simply couldn’t keep pace with the volume, so code began merging unread, and that became normal. The detail I keep returning to is that teams with mature, disciplined engineering practices were hit just as hard as everyone else. Good process didn’t protect them, because the volume arrived faster than any process was designed to absorb.

CodeRabbit studied 470 open source PRs in December 2025, 320 AI-coauthored and 150 human-only, and found the AI changes carried roughly 1.7x more issues. Logic and correctness problems were up about 75%, security issues were 1.5 to 2x more common, and readability problems more than tripled. The company’s AI director, David Loker, described these as “predictable, measurable weaknesses that organizations must actively mitigate.” Predictable is the operative word. These are known, locatable weaknesses, which is good news: It means a review process, human or automated, can be aimed straight at them.

One caveat to hold throughout: CodeRabbit and Faros both sell into this market, so their framing is not disinterested. That doesn’t make the numbers wrong—the effect sizes are large and consistent across unrelated sources—but vendor research deserves to be read with that in mind.

GitClear has the single number I would lead with. In its productivity data through 2025, daily AI users produce around 4x the raw output of nonusers, but measured against their own output a year earlier, the real productivity gain is only about 12%. You’re generating roughly four times the code for something like a tenth more delivered value, and a human still has to review all of it. To GitClear’s credit, CEO Bill Harding is explicit that some of even that 12% is selection bias, because stronger developers are concentrated in the AI cohort.

GitHub reports that Copilot review has now run over 60 million reviews, a 10x increase in under a year, and more than one in five reviews on the platform involves an agent. This is no longer a niche practice. It’s how code gets made.

Four datasets, four methods, one conclusion. We poured machine-speed output into a system built for human-speed work. The bottleneck didn’t disappear; it moved to verification, and review is where that bill comes due.

Everyone is solving a different problem

How much review a change needs depends almost entirely on its blast radius, and most advice you read was written by someone operating for a very different one.

Almost all the alarming data above comes from enterprise telemetry and from open source maintainers being overwhelmed. It’s entirely real if that is your situation. If you’re one person shipping something a handful of people will ever run, much of it simply doesn’t apply to you, and you shouldn’t be made to feel otherwise.

Three variables determine where you sit:

  • Blast radius: What happens when it breaks? Nothing, or angry users and money and PII on the line?
  • How long the code lives: A throwaway prototype you might rewrite next week, or a codebase you’ll maintain for years?
  • How many people need to understand it: Just you holding the whole thing in your head, or a team that has to share ownership over time?

Run the same diff through those three variables, and “good review” means genuinely different things.

If you’re working solo on a greenfield project with no users, review’s second job, distributing knowledge across a team, doesn’t exist for you. You are the team. The reasonable move is to lean hard on tests and automation, review the parts that genuinely matter, and accept a lighter touch on the rest. Duplication and churn cost far less when the code may not exist in a month and nobody is paged at 3:00am when it breaks. The catch, and people learn this one painfully, is that it only works if the tests are real. Skipping review without a safety net doesn’t remove the work. It defers it at a higher price, and standards slip when no one is there to push back. “No users” is permission to defer review. It isn’t permission to skip verification.

Then the project gets users. This is the dangerous middle, and the crossing is rarely noticed at the time. Review’s bug-catching role suddenly matters, because bugs now hurt people, and its knowledge-sharing role switches on, because it’s no longer only you. Teams keep their solo-era habits a few months too long, and then there’s a postmortem and the Faros numbers stop being a chart and become their own dashboard.

At the far end is the large organization with an old codebase and many users. Here every alarming figure lands at full strength. A duplicated helper isn’t a style nit; it’s a future bug surface and a maintenance cost that compounds for years. A change nobody understood is comprehension debt that becomes someone’s on-call incident. Review is doing several jobs at once, and the volume of agent output quietly breaks all of them. The Faros finding about mature teams is aimed squarely here.

So the point is not “Enterprises should be cautious and solo developers can relax.” It’s that the purpose of review changes with your position, so the rules have to change with it. Bolt an enterprise’s locked-down multi-agent evidence-required pipeline onto a two-person prototype and you’ve added friction for no benefit. Run “tests pass, ship it” on a payments system and you’ve built an incident generator with a green checkmark on top. Most bad advice in this space is one position on that spectrum prescribing to another.

What review is actually for now

Review was built to check an author’s reasoning. An agent does reason, but that reasoning is usually thrown away rather than attached to the code, so the reviewer has to reconstruct a rationale that never made it into the diff. The good news is that this is a tooling problem, and capturing the reasoning makes review dramatically easier.

This is the part that genuinely changed, and I think it is underappreciated.

When a human writes code, intent comes along for free. The reasoning, the alternatives weighed and discarded, lived in the author’s head, and review was you checking that reasoning. Modern agents do reason, often visibly, producing thinking traces and weighing options and explaining themselves as they go. The catch is that this reasoning is usually discarded the moment the diff is produced. It’s rarely captured and rarely attached to the PR, and in any case it is the agent’s reasoning about how to implement the task, not a human’s judgment about whether it was the right task to begin with. So review shifts from checking reasoning that sits in front of you to reconstructing intent that never got written down, which is harder and slower, and we keep acting surprised that it takes 441% longer.

A 2026 paper, “AI Slop and the Software Commons,” analyzed 1,154 posts across 15 Reddit and Hacker News threads where developers discussed “AI slop.” One line from a developer has stayed with me: reviewing an agent’s PR made them “the first human being to ever lay eyes on this code.”

That sentiment points straight at the fix. In normal review, the author already understood the change and you were checking their work. With an agent PR, nobody has reconstructed the why yet, and the reviewer is the first to try. As the paper puts it, review “wasn’t built to recover missing intent.” The encouraging part is that missing intent is recoverable: The reasoning existed; we just discarded it. Have the agent state what it was trying to do and what it ruled out, then capture it as a decision log on the PR, and a large part of the reconstruction cost disappears. This is a tooling problem, and tooling problems get solved.

None of which makes “have the AI review the AI” a complete answer on its own. A second model with different priors genuinely catches real bugs, and it catches a lot of them, which is why you should run one. What it doesn’t supply is the human judgment about whether this is the right change to build in the first place. That judgment stays with a person, and it happens to be the most interesting part of the job and the part worth keeping.

The tools are good, but not always for the reason they advertise

The current AI reviewers are genuinely good, and they occasionally don’t flag the same lines as each other, so the right move is not picking the best one but running two that are built differently.

The dedicated AI review tools are good now, and I think you should be running at least one on everything, side projects included. CodeRabbit is the most widely deployed and topped the independent Martian benchmark (January to February 2026) on F1, at around 49% precision with the best recall in the field. Greptile trades precision for recall, with around an 82% bug-catch rate against CodeRabbit’s 44% in one benchmark, at the cost of more false positives. Anthropic’s Code Review reports under 1% of its findings marked incorrect by their engineers; the figure I would actually show a manager is that it raised their internal rate of PRs receiving a substantive review from 16% to 54%. The long tail of changes that used to get a glance and an approval now gets read by something.

The most useful result I have seen this year isn’t from a vendor. An engineer ran four reviewers in parallel, CodeRabbit, Sentry Seer, Greptile and Cursor BugBot, across 146 real PRs and 679 findings over three and a half weeks:

Of 617 distinct flagged locations, 93.4% were caught by exactly one of the four tools. 6% by two. Almost none by three. None at all by all four.

The four tools never once flagged the same line. Each was strong at a different class of problem: Greptile with near-zero false positives on correctness and architecture, CodeRabbit with the widest net and one-click fixes, and Seer best on production-failure severity. That is the adversarial review argument demonstrated on a real codebase rather than in a paper. Heterogeneity is the whole point. Four copies of one model is a single reviewer with a larger invoice, whereas four genuinely different reviewers surface a set of bugs no single member could find alone, the human included.

In practice: Do not agonize over the single best tool because there isn’t one. At the high-stakes end, run two with deliberately different characters. (The experiment above paired Greptile for everyday correctness with Seer for production-failure severity, with almost no overlap.) If you are solo, one good reviewer plus real tests is plenty. And whatever the marketing says, measure it on your own code, because every one of these results was specific to a particular codebase, and yours will be too.

Should we just let AI review more of it?

The machine is already reviewing more of your code than you are. The only real decision left is whether you do that deliberately, and the amount of human you keep should scale with your blast radius.

I keep hearing a question from experienced engineers that would have been heresy a year ago: Should the machine be doing more of the reviewing, perhaps most of it? I no longer think that’s a foolish question.

The uncomfortable part is that AI review works. Under 1% of Anthropic’s findings are marked wrong; the tools catch bugs humans read straight past, and they don’t get tired on the 30th PR of the day, which is exactly when a human is least reliable. Meanwhile humans are visibly not keeping up: Zero-review merges are up 31% and review times are up triple digits. In a real sense the machine is already reviewing more of the code than we are. The honest framing is not “Should we let AI review more?” but “AI is already doing it, so are we going to be deliberate about that or let it happen by default while pretending humans still read everything?”

Loop engineering sharpens this. The premise of a loop is that you stop being the person who prompts the agent and instead build a system that prompts it, and a central part of that system is a judge: an agent that decides whether the work is done before moving on. The reviewer is the next role being designed out of the inner loop, on purpose. We spent a year automating the writing, and the loops are now automating the checking, and the human keeps getting pushed up and out. “Where does the human stay?” is not a seminar question; it’s something you decide every time you wire up a loop, whether or not you realize you’re deciding it.

Where I currently land, and I hold this loosely: The answer is not “a human reads every line.” That’s over. The volume ended it, and anyone insisting otherwise is describing a world that no longer exists. But it’s also not “let the loop review itself and walk away.” When an agent writes the code, another reviews it, and a third judges it, you’ve a closed loop of models with broadly correlated blind spots, especially when they come from the same family, confidently agreeing in the same places. A confident “looks good” with no human anywhere in it is borrowed confidence: The system’s certainty becomes yours, and nobody actually understood anything. The loop can be both very sure and very wrong, with no human left to tell the difference.

So the human doesn’t leave; the human moves up a level. You stop reviewing every diff and start owning the parts that do not transfer to a model. Accountability, because you can’t page a model at 3:00am. The judgment of whether this is even the right change to build, as distinct from whether the code is correct. The high-blast-radius gates where being wrong is expensive. And the awkward one: the behavior nobody specified, because a model reviews the code that exists and rarely flags the requirement that nobody thought to write down, which remains a human-shaped gap I don’t expect to close soon. Human in the loop becomes human on the loop: sampling, spot-checking and auditing the system rather than reading every PR, and spending your limited attention where being wrong would actually hurt.

This is already how I work on my own projects, including the open source ones that now see more PRs in a day than I could carefully read in an evening. I point Claude Code or Codex at a batch of incoming PRs and ask for a first pass: a high-level read of what looks safe to merge, what needs more work, and what’s genuinely high-risk. I don’t auto-merge on the result, and I don’t lazy-merge whatever it approves. What it gives me is a way to allocate attention. I can spend a few minutes confirming the changes it considers low risk, and put real, careful time into the ones it flags as dangerous. The detail that matters is that this isn’t my old review hour made slightly faster. It’s a different shape of hour, and at the volume I now deal with, it’s the main reason the queue stays survivable at all.

Codex and Claude Code giving me a first-pass, risk-sorted read of a batch of PRs. The triage is the help. The merge decision stays mine.

A more extreme version of the same move is Kun Chen, an ex-Meta L8 engineer now shipping around 40 PRs a day as a solo builder, who has largely stopped reviewing code. It would be easy to dismiss this, except he is an L8, unusually good at the thing he stopped doing. He runs 20 to 30 agents in parallel and has moved his effort into the plan: He writes detailed plans up-front; the agents run for hours against them, and he says plan quality determines how long they can run unattended. That’s the move I described above in its purest form. It’s worth being precise about what actually happened, because it is not that he stopped verifying. The intent didn’t vanish; he wrote it down himself in the plan, so the “first human to ever lay eyes on this” problem is half-solved. A human did understand the why, just up-front rather than after. And he didn’t work without a net. He built an automated review gate (which he calls No Mistakes) that checks the code before it merges, and he stays on escalation when an agent gets stuck. The human does the expensive thinking before the code exists, and the machine does the line-by-line afterward, which may well be the shape of where this goes.

But he’s a solo builder with no large team and no decade-old system full of landmines beneath him. The exact conditions that make 40 PRs a day without review rational for him are conditions most readers don’t have. Copy his workflow onto a team shipping to many users and you reproduce the Faros numbers on your own dashboard. Kun isn’t wrong; he’s just a long way down one specific end of the spectrum.

Which is the spectrum point again. Solo with no users: Letting AI review almost all of it is a defensible 2026 position, and you shouldn’t feel guilty about it. Maintaining something large for many people: Let the machine handle the first pass, the second pass, and the boring 90%, but keep a real human on the load-bearing paths and don’t let the loop close completely on anything that can hurt someone. How much human you keep is a dial, and you set it by blast radius, not by guilt.

What to actually do

Stop reviewing everything to the same depth. Spend scarce human attention only where being wrong is costly, and let cheap deterministic gates and AI reviewers handle the rest.

The organizing idea is to match review effort to the cost of being wrong, push the cheap deterministic work as early as possible, and reserve human attention for what only humans can do.

Tier by risk, not by author. A config change earns a linter and a glance. A payments path earns the full stack: types, tests, two different AI reviewers, a human who owns that system, and a security pass. Don’t spend a heavy review on boilerplate, and don’t wave through an auth change because the tests are green. The layered approach is the same everywhere; what changes is how many layers a given diff has to clear.

Fast-fail the expensive tail. The most useful recent finding for teams drowning in agent PRs is “Early-Stage Prediction of Review Effort” (January 2026), which studied 33,707 agent-authored PRs. Agents are good at small, well-defined changes. Around 28% merge almost instantly, but they tend to “ghost” the moment they get subjective feedback, abandoning the back-and-forth that review actually is. (A companion 2026 paper found reviewer abandonment accounted for 38% of rejected agent PRs.) The researchers built a “circuit breaker” that predicts high-maintenance PRs from cheap signals like file types and patch size before a human looks, and it works well. Triage agent PRs up front, fast-track the trivial ones, and don’t let a person sink an hour into a sprawling change the agent will abandon as soon as you push back.

Raise the bar for what you will even review. The fix for being buried isn’t locking down the repository. It’s refusing to review changes that arrive without evidence. Require, before review, a statement of what the change is for, a diff that isn’t 3,500 lines with no comments, the test output, and proof it was actually run. This is how you stop being the first human to read the code. You push the intent-reconstruction work back onto whoever submitted it, where it’s cheap, rather than absorbing it yourself, where it is expensive.

Keep PRs small, deliberately. Agent PRs run large, 51% larger on average in the Faros data, and reviewer engagement is one of the strongest predictors that a PR merges at all. A large unreviewable PR gets rejected outright or, worse, rubber-stamped. Instruct your agents to produce small commits. A diff a human can actually read is now a design constraint, not a courtesy.

Read the test changes more carefully than the code. This is the agent failure mode to watch. The agent changes behavior, then “fixes” the test by rewriting the assertion to match the new, broken behavior. A green check over 200 edited tests means nothing until you have confirmed the edits were correct. Treat any diff that rewrites many tests as a flag and read those first. Mutation testing earns its place here: Coverage tells you a line ran; mutation testing tells you whether the test would notice if that line were wrong.

Treat CI as the wall that doesn’t move. Watch for the patterns GitHub now warns reviewers about: removed tests, skipped lint, lowered coverage thresholds, a duplicated helper that already exists elsewhere, and untrusted input flowing into a prompt. That last one deserves emphasis, because agent-built features are a fresh source of prompt injection: If a change pipes user-controlled text into an LLM call without thinking about what that text can instruct the model to do, the vulnerability isn’t visible in the diff. It’s latent in the data that will arrive later. Agents will also weaken CI to make themselves pass, not maliciously, just gradient descent finding the cheapest path to green. Deterministic gates are the one part of the pipeline that can’t be talked out of their verdict by a confident paragraph, so keep them strict.

A human owns the merge. A model can’t be paged and can’t be held responsible for what it shipped, so whoever clicks merge owns it. When an AI review says “looks good” in a calm, confident voice, it’s handing you confidence it hasn’t necessarily earned. Treat every AI review as a sensor, not a verdict: data, not a decision.

If you are solo with no users, the tiering, the test-change discipline, and CI are most of what you need; the rest is overhead until people show up. If you’re a large organization, all of it is the baseline, and the triage and intake bar are the difference between a review process that scales and one that quietly collapses.

What this means if you run a team

The bottleneck is no longer how fast you write code. It’s how fast a trusted human can be confident in a review. Cutting the people who provide that confidence because “AI made us faster” simply converts the saving into future incidents.

The binding constraint on shipping is now how fast a trusted human can be confident a change is correct. Any plan that treats generation as the bottleneck and review as free will quietly stall, with the velocity dashboard staying green the whole way.

The Faros report is direct about this: QA and review work rises even as output rises, so reducing engineering headcount because “AI made us faster” is dangerous unless you have closed the review gap first. The senior-engineer tax (review time up by triple digits) falls hardest on the people you can least afford to bottleneck, and it is invisible to any metric that only counts merged PRs.

Open source maintainers hit this wall first and hardest. The steady stream of plausible but hollow contributions costs real triage time even when those contributions are well-intentioned, and that’s the canary. Companies are next. The ones handling it well treat review capacity as a real resource to be measured, protected, and spent deliberately, not as slack that AI has freed up.

Writing got cheap but understanding didn’t

Code review didn’t become less important when agents arrived. It became the central activity. Writing code is increasingly solved and getting cheaper by the month; the durable advantage is the system that lets you trust what was written.

Don’t take the one-size answer in either direction. If you’re solo with no users, the enterprise horror stories about churn and duplication are a future risk, not today’s fire, so lean on your tests, review what matters, and stay honest that the deferred work is still owed. If you maintain something large for many people, every alarming number here is about you, and the only thing that holds is a tiered, evidence-required, deliberately heterogeneous review process with a human owning the merge.

What’s constant across the whole spectrum is the underlying economics. We made writing cheap, and understanding stayed exactly as expensive as it has always been. The teams that do well over the next few years won’t be the ones generating the most code; they’ll be the ones who built a review system they can actually trust, and who never confuse “the tests passed” with “a person understands what this does and why.”

Or, as Simon Willison keeps putting it, “your job is to deliver code you have proven to work.” Agents haven’t changed that. They have made “proving” the center of the job rather than an afterthought, and I think that’s a good trade. Understanding a system well enough to stand behind it is the most durable and most interesting skill in software, and there has never been a better time to get extraordinarily good at it.

[$] Initiating writeback earlier [LWN.net]

Writeback is the process of ensuring that dirty pages or folios in the page cache are flushed to the disk, so that changes to those files are made persistent. In a filesystem-track session at the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit, Jeff Layton wanted to discuss whether the writeback operation should be initiated earlier than it is today. The consensus seemed to be that it should be done earlier, but the path toward making that happen was less clear.

18:14

Meta Is Testing Facial Recognition for Police and Military [Schneier on Security]

We know that ICE wants to deploy eyeglasses with facial recognition that can identify people in real time.

Turns out Meta is prototyping the feature with a Pentagon supplier. (Alternate news story.)

17:56

Reproducible Builds (diffoscope): diffoscope 322 released [Planet Debian]

The diffoscope maintainers are pleased to announce the release of diffoscope version 322. This version includes the following changes:

[ Zbigniew Jędrzejewski-Szmek ]
* Add a local version of the (deprecated) os.path.commonprefix method.

You find out more by visiting the project homepage.

17:35

Link [Scripting News]

When Claude has all the information available it can figure out stuff a human mind would never be able hold in our minds at the same time, but it often doesn't remember to get the information first. When you get to the level I'm at with this, it's hallucinating all the freaking time because it didn't load the part of the data set that had the answer. It was right there, it was supposed to know, it just forgot to look. My job is to recognize when it has done that and tell it to go read handoff.md again. I mentioned this on Twitter, and got all kinds of help, but the terminology isn't well known to me. Still diggin, as they say.

17:07

16:21

16:07

Lots of stories about systemd v261 [LWN.net]

Lennart Poettering has posted a list of Mastodon posts about the changes in the systemd v261 release. The Mastodon format makes the reading harder, but there is a lot of useful information there.

15:21

Link [Scripting News]

I'm loving Star City. New episode last night, wow.

A project I wanted to do with WordPress [Scripting News]

I was on Slack chatting with a friend from WordCamp Canada last year, and by accident (I guess) Slack sent me the first message they sent after coming home about all the things we'd do. It reminded me of how possible things seemed then, and for a moment I got lost in planning it out, and I absolutely loved what I saw there. But it was sad, because I am sure it will never happen, not until someone inside the community gets the idea, and there really is only one "someone" here. Heh. I've been around big companies and communities before, many times. Anyway, I figured I should post this here now, because I have moved toward a WordPress-less web, or WordPress-on-the-Side, but I want to be clear that WordLand remains in place, free for anyone to use. It's a great way to write for WordPress. And if this project to make web content APIs a web standard, I'm totally on board for helping the world understand how potent an idea it is.

So here's the text of the message with light redaction in places. ;-)

  • it's funny when i got email notice for this post, it sent me the first message you sent after the wordcamp in ottawa. those were more optimistic days. i still have my wordpress work, but now have pivoted to working on the web without the wordpress connection since matt seems to want to go in a different direction, based on all the stuff they've started re AT Proto, which imho is a terrible bet. it would be like the Knicks trying to move from NYC to Mississippi. Why would you do that when so many developers know wordpress and you all have such an excellent api?
  • you asked me back then if there's part of your project i'd like to work on, and i said i'd think, and i had an idea just the other day, thought i should share it.
  • the wpcom api is fantastic and very few people know about it, even the people in the wp developer community. but it really is the answer -- how will services that work on the social web coordinate? where will users store their data? where will the published results be available to read? wordpress really is the best choice. i have no stake in that, i don't own wordpress, have never made a dime off it, i'm just me, saying that and i have some credibility in this area.
  • so here's what i suggest
    1. a new simplified version of the api and some example apps, both are already done
    2. a new protocol so that any service can be part of it, we need a way to identify servers that aren't using jetpack or wordpress.com
    3. a new name and website, and positioning -- something to roll out.
    4. work with independent developers to make their products work
    5. co-marketing
    6. investment and distribution
  • i know a lot about all these things, having done them before with some amount of success.
  • i'm about to embark on it again with my new product, btw called rss.chat. i think you can imagine what it is based on that name?
  • but i haven't forgotten about this opportunity. i don't know how much of 1-6 the open source project, but #2 is clearly in your purview. not something people are going to want automattic to do (though I'm sure they could). with the new protocol look what we have! a way to distribute apps on the web so that developers don't have to compete with BigCo's, they can be a person with a hobby, and who knows they may have a big hit and get rich.

Hello World [Scripting News]

This is always good for a chill.

[$] What's coming in Git 2.55 [LWN.net]

The Git v2.55.0-rc2 testing release appeared on June 23, suggesting that the final Git 2.55 release can be expected in the near future. While this Git update lacks radical new features, it does include a number of improvements that regular Git users will appreciate, including commands to easily edit the commit history, more formatting options, fsmonitor support for Linux, and more.

14:35

Link [Scripting News]

With all the Democratic Socialists winning over standard Democratic party incumbents, there's a fair amount of angst on the cable news. If they're scared, they should step aside. We tried it their way in the Biden Administration. If we ever get lucky enough to have a president who's sane and wants to reboot democracy, it's going to require doing some things that an oldtime president wouldn't want to do, like Obama or Biden. Both of them gave up without even trying. Forgive them, but let's not make the mistake of electing their successors. It's time for clear-thinking people to take office, fully aware of what they signed onto, and then if we elect them, they do it. And when the Repubs throw bullshit at us, say it's bullshit, and say it that way, not the mealy-mouthed way Jeffries does, or even Elizabeth Warren. What we need now is a strong dose of Bernie Sanders. Did I ever think I'd say that? Hell no.

Security updates for Friday [LWN.net]

Security updates have been issued by AlmaLinux (buildah, coreutils, evince, libpng, libreoffice, libtasn1, libxml2, libxslt, nginx, nginx:1.24, nginx:1.26, postgresql:12, python-urllib3, python3.12-urllib3, python3.14, python3.14-urllib3, skopeo, tigervnc, tomcat, and vim), Debian (chromium, dnsdist, giflib, libdbi-perl, libssh2, libtext-csv-xs-perl, pdns, pdns-recursor, python-urllib3, and sogo), Fedora (goose, httpd, librabbitmq, perl-Compress-Raw-Bzip2, perl-DBI, perl-IO-Compress, perl-Socket, python-django-allauth, rsync, and strongswan), Oracle (389-ds-base, buildah, containernetworking-plugins, coreutils, evince, fence-agents, giflib, git-lfs, hplip, krb5, libcap, libexif, libtasn1, memcached, opencryptoki, podman, postfix, postgresql:12, postgresql:13, postgresql:15, postgresql:16, python-urllib3, python3.12-urllib3, python3.14-urllib3, python3.9, runc, skopeo, tigervnc, vim, webkit2gtk3, xorg-x11-server, and xorg-x11-server-Xwayland), SUSE (apache-commons-configuration2, apache-commons-text, apache2, containerd, kernel, libnilfs3, libopenbabel8, libtar, libzypp, lrzip, nodejs24, ofono, perl-Net-Dropbox-API, podman, python-pip, python-PyJWT, python311-aiohttp, python311-nltk, python311-python-multipart, python312, and python315), and Ubuntu (amd64-microcode, containerd, containerd-app, containerd-stable, cpp-httplib, imagemagick, mina2, node-pbkdf2, NSD, and xrdp).

The "Akrites" vulnerability-mitigation project launches [LWN.net]

The Linux Foundation, in a letter co-signed by a large range of organizations and companies, has announced the launch of "Akrites", a project to fast-track vulnerability fixes into projects.

As Akrites works upstream to fix projects at the source, we commit to support downstream efforts to secure critical infrastructure before it can be exploited. When patches are released to the public, adversaries are able to utilize AI to rapidly reverse engineer the underlying vulnerabilities, develop exploits, and launch attacks. The success of our efforts therefore will be measured in patch deployment, not publication. We will partner with critical infrastructure owners and operators, civil society efforts, and governments as they increase coordination to achieve these goals.

Confidentiality is non-negotiable: An undisclosed flaw in a widely deployed package is, in effect, a weapon, and the program is built first to prevent leaks. Fixes flow back into each project's own home, working with the maintainers. The engineering resources and other capabilities provided by Akrites participants contribute to this effort. Additionally, when a critical package has no one maintaining it, Akrites will stand as the maintainer of last resort so a fix can still reach everyone in a timely fashion. We will also align with government efforts so that public and private defenders move together, rather than in a disjointed fashion.

14:07

Error'd: Fi fa foe [The Daily WTF]

First up this week is a little story about a fifafail. I do wonder if this was a failure of the television station, or whether there was something more to it than that.

Hercules wrote to alert us to these World Cup shenanigans, explaing "At least the flags were correct. And yes, this was live TV. The host got the country names correctly, and even called out that the written text was wrong"

5503f1d7141948f88f4650c17468ff46

"I'm very open in my job search but I did limit it to France. The search has been working well for months, but this morning I got a bevy of new interesting propositions. It seems France is much bigger than it was yesterday." Apparently WorkerNumber29200 is surprised by the expansionist nature of an imperialist coloniser. Plus ça change, Worker.

f05fd09185bd4f2ebeacc92de9609131

We have a couple of wtfs from Github. First Hans K. "would love to find a, so I could fix this GitHub Dependabot issue."

4d41995a2e7a423cbf8de6e960b876c4

And Peter S. figures that "GitHub has trouble doing basic math -- or they have an unpublished proof that 0=1"

e954781458d64f6da02bfad014efc854

Finally Michele has just encountered one of the most maddening phenomena on Amazon recently. "Searching for a cheap USB-C fast charger. Got a list of expensive CDs of obscure artists." All of them AI-generated, like the 100000 Whys books?

cdf7c2baae7541a9ad8e90b9c4ecb0c4

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!

13:00

This Week in AI: Who Controls the Loop? [Radar]

This week host and Turing Post founder Ksenia Se threaded the latest news into a single argument: AI is moving out of conversation and into the operational loops where real work happens. From SpaceX’s $60 billion acquisition in the developer tools market to the G7’s debate about frontier model access to image generation company Midjourney’s pivot to medical hardware, the stories all pointed in the same direction.

When agents own the loop, the IDE becomes infrastructure

SpaceX’s acquisition of Anysphere, the company behind Cursor, for a reported $60 billion in stock is the kind of deal that looks straightforward until you think about what Cursor actually is. On the surface, it’s a popular AI-assisted code editor. (It’s also one of many in a highly competitive market.) However, Ksenia argued that that’s thinking too small, especially for Elon Musk. SpaceX may be angling to position Cursor as the new center of software work, in the same way GitHub became the center of the previous era.

In the old model, GitHub owned the pull request. But in the new model, the question of who owns the full loop where agents read a repo, write code, open pull requests, run tests, handle failures, and enforce engineering standards is still open. GitHub still owns the system of record and is moving to defend it: Chief product officer Mario Rodriguez recently told Turing Post that GitHub’s mission has shifted from human-developer collaboration to developer-and-agent collaboration, with the platform becoming agent-native across its APIs, UX, and underlying infrastructure. But as Ksenia explained, “Cursor’s advantage is that it owns the developer’s active coding surface” where the work starts.

If agents write more code than humans, software infrastructure should be redesigned around agents from the start. Cursor was built for agents. GitHub was built for humans and is now playing catch-up. That architectural choice may matter more than any individual product feature.

Frontier AI access is becoming a geopolitical question

The G7 summit this week included discussions about a “trusted partners” framework that would give select allied nations access to advanced US AI models, following a US order that restricted foreign nationals from accessing Anthropic’s frontier systems on national security grounds. AI models that can write software, find vulnerabilities, and operate across tools are capability systems, not just productivity software. The access rules are catching up to that reality, although as Ksenia noted, things haven’t yet come into complete focus.

For a long time, AI regulation sounded like: How do we label synthetic media? How do we reduce hallucinations, prevent bias, make chatbots safer? Now the question is so much bigger. Who can use these capable systems? Can allies use them? Can cybersecurity firms outside the US use them? Can non-US employees at US labs use them? Can European companies use American models if those models are also strategically sensitive? This isn’t traditional software licensing anymore. This is capability access control.

The underlying tension behind the G7 conversation is the dual-use problem: A model capable enough to find software vulnerabilities for defense can also find them for offense. The “trusted partners” framework reflects the new geopolitics of AI as countries jockey with rivals to secure strategic benefits for themselves and their allies. It represents an alliance layer for AI access that applies access structures previously reserved for physical military hardware to capabilities too strategically important to make fully open and too useful to keep entirely locked down. As Ksenia noted, the alliance is “not literally NATO, but [it is founded on] the same kind of logic.”

But access restrictions might also impact the talent that built these systems, who are increasingly not citizens of the country trying to control it. For instance, AI researcher Andrej Karpathy, recently hired by Anthropic, is publicly described as Slovak-Canadian. If access controls apply to non-US citizens, he and others like him may be denied access to the very systems they’ve been hired to work on. It’s an area we’ll continue to watch closely.

AI is entering the measurement loop

Midjourney, the company you probably associate with AI-generated images, has announced a new medical division and a full-body ultrasound scanner built around water immersion, developed in partnership with medical imaging hardware maker Butterfly Network. The device is designed to scan the entire body in 60 seconds: A person descends into a shallow pool on a motorized platform, passing through a ring of roughly half a million ultrasound sensors, each functioning as both a transmitter and receiver. The system uses over two petaflops of processing power to reconstruct a 3D body map from the returning wave data. Midjourney says the resulting images look comparable to today’s MRI output at a fraction of the cost and time, though that claim still needs serious clinical validation before it can stand.

The current prototype uses 40 Butterfly ultrasound-on-chip devices per system, according to a disclosure from Butterfly Network, which confirmed its codevelopment and licensing agreement with Midjourney. Midjourney plans to open a facility in San Francisco in 2027, embedding its device in a spa environment alongside hot tubs, saunas, and cold plunges. Diagnostic medical uses will require FDA approval; the initial focus is body composition mapping.

If Midjourney can build a library of full-body scans taken over months and years, that longitudinal record would give doctors and AI health tools a level of baseline data that doesn’t currently exist at scale outside of clinical trials. That’s the same structural logic Ksenia traced through Cursor and GitHub: The value compounds inside the loop through repeated, precise measurement over time. Midjourney is positioning itself to own that loop in the health domain.

What’s next

The competition for AI advantage is moving from model capability to infrastructure position. Who owns the coding loop? Who controls access to frontier systems? Who builds the measurement environment where health data accumulates over time? Those questions are about where intelligence meets operational reality, not which model scores highest on a benchmark.

Hiring news from the week reinforces how seriously the labs are treating this phase. John Jumper, the Nobel laureate who shared the prize with Demis Hassabis for AlphaFold, left Google DeepMind for Anthropic. Noam Shazeer, one of the coauthors of “Attention Is All You Need,” reportedly left Google for OpenAI after Google paid approximately $2.7 billion to bring him back in 2024. The labs are betting on scientific talent at the same time they’re betting on infrastructure.

Next week, host Andreas Welsch will be back to discuss multi-vendor strategy with Conductor’s Matt Palmer. They’ll cover Sakana’s launch of Fugu, Qualcomm’s ~$4B move for Modular, Anthropic’s Claude Tag stepping into Slack as a virtual coworker, Samsung putting ChatGPT and Codex in front of its entire workforce, and more. Register here to attend live.

Starting in July, registration for the live event will be open only to O’Reilly members. (If you’re interested, try O’Reilly out for free.) We’ll continue to publish our takeaways here on Radar each Friday and share full episodes on YouTube, Spotify, and Apple.

12:14

One Million Passports Leaked Online [Schneier on Security]

A database of almost a million passports from around the world was leaked online.

Note what happened. A high-value credential—a passport—was used in an ancillary low-value authentication system: ID verification for cannabis dispensaries. And it’s the low-value system that got hacked, putting the high-value credential at risk.

11:49

Trip Of A Lifetime [QC RSS v2]

there's a software emulation for everything

10:42

You don’t need a better camera [Seth's Blog]

They keep getting fancier. But you would benefit from investing in better lighting instead.

It’s tempting to upgrade your computer processor, your frying pan or your sneakers as well.

The thing is, once the foundational tools are good enough, technique and training outperform hardware. New snow tires are often more effective than a new car at getting to work, because traction matters more than horsepower.

Sharpening your saw or building resilience might be the best way to improve.

08:28

Imperium Maledictum [Penny Arcade]

New Comic: Imperium Maledictum

05:49

It’s A Very Exclusive Club [Ctrl+Alt+Del Comic]

My boys love sleepovers. And we do a lot of them, I think. I did sleepovers when I was a kid, but I seem to recall them being more of a special occasion kind of thing. My kids want to have friends over constantly; almost every hang-out tends to include a request at some point […]

The post It’s A Very Exclusive Club appeared first on Ctrl+Alt+Del Comic.

Girl Genius for Friday, June 26, 2026 [Girl Genius]

The Girl Genius comic for Friday, June 26, 2026 has been posted.

04:42

Russ Allbery: Review: Platform Decay [Planet Debian]

Review: Platform Decay, by Martha Wells

Series: Murderbot Diaries #8
Publisher: Tor
Copyright: 2026
ISBN: 1-250-82701-9
Format: Kindle
Pages: 245

Platform Decay is the eighth book in the Murderbot science fiction series. You absolutely should not start here, but you also don't need to remember the specifics of the previous books.

As the story opens, Murderbot and a friend (the identity of whom is a spoiler for previous books) are infiltrating a Corporation Rim torus, a massive space station that encircles a mined-out planet. (Like most science fiction megastructures, this is more space than the plot really requires.) Murderbot's mission is to exfiltrate some of Dr. Mensah's family members who have become entangled in corporate shenanigans. The corporates are eager to get revenge for the events of System Collapse, not to mention the other times Preservation Station has upended corporate plans. Murderbot's job is to stop them.

The group, in addition to one of Dr. Mensah's partners, includes an older woman and a young child. Murderbot is analytical and of course not at all emotional about children, which is reliably a good time. Also, the older woman is gruff, stubborn, and thoroughly enjoyable.

There are, of course, complications that lead to picking up more children and going through rather more of the torus than Murderbot wanted to explore. Each section of the torus is run by a different corporation and has a different constructed environment and visual aesthetic, so there are a lot of opportunities for fights, daring escapes, and incidental trouble.

Also, well:

So I had installed a mental health module. I know, I was surprised I did it too.

After the events of System Collapse, University Medical decided that Murderbot needed a bit more metal health support.

The only reason I agreed to it was that the mental health module didn't actually try to adjust my processing or core programming or anything; it just monitored my organic neural tissue. When my neural tissue started to generate weird chemicals and whatever, it would ping me to "check in with my emotional state." Seriously, I could have coded that myself.

(I told Dr. Bharadwaj that, and she said, "Would you have ever coded that yourself?" which was totally unfair and also correct. I would never have done that.)

Speaking as someone whose neural tissue sometimes generates weird chemicals and whatever, I sympathize.

The specific form this module takes is periodic "emotion check" parentheticals throughout the narration, which I found utterly delightful.

I ran that through risk assessment and it produced the equivalent of a shrug.

(Emotion check: Shrug sigil right back at you, you piece of shit.)

This is otherwise an extended action movie sort of a book, much like several of the early novellas. There are no major political or interpersonal developments here and the usual cast (apart from Murderbot) is mostly absent. Instead, we get an extended, dangerous journey through a corporation-controlled habitat, mixed with Murderbot trying to interact with humans in a way that minimizes its annoyance while being hopefully reassuring. It's competence porn with awkward but surprisingly heartfelt emotional bonding, not that Murderbot in any way wants to bond or would appreciate that description.

I doubt this will be anyone's favorite entry into the series since there are none of the big reveals or major leaps of character development there have been in the past few books. But, like all Murderbot books, the narrative tone is wonderful and all of the small asides and little moments of character interaction are an utter delight. If you've gotten this far in the series, you know what I mean and you'll be as happy to read more of it as I was. There is a part of me that is hoping for some major plot development, and I always want to see more of ART (who has no significant role in this book), but Wells has the narrative style down so perfectly that I would read and enjoy a book about Murderbot doing just about anything.

If you're this far in the series, you probably don't need a review, and since this is an action-heavy adventure rather than a character growth novel, I don't have a lot more to add. There's a new short Murderbot novel out and you want to read it. Recommended to everyone who enjoys the series.

Rating: 8 out of 10

02:21

01:35

Thursday, 25 June

23:49

Rebuked for wanting to raise taxes on wealthy [Richard Stallman's Political Notes]

A conversation between a Labour minister and Ambassador Mandelson rebuked Labour MPs for wanting to raise taxes on some people who could afford to pay more. Another minister said this was embarrassing.

It should be extremely embarrassing for Labour to be exposed as ridiculing the idea of raising taxes on the rich. That is exactly what it must do to reduce the poverty than has been increased by directing an ever-increasing fraction of society's wealth to the rich.

Activists moved to solitary confinement [Richard Stallman's Political Notes]

Alabama moved three activists, who lead protests against prison conditions, into solitary confinement.

Laura Wittmann resigned from Uline [Richard Stallman's Political Notes]

*Laura Wittmann resigned from Uline in condemnation of the company owners' active support for fascism in the US.*

Appeasing bond markets [Richard Stallman's Political Notes]

"Appeasing bond markets" — prioritizing keeping interest rates for government bonds low — is supposed to bring "stability", but in the UK it means a steady decline in the productive economy.

A government has a practical need for low interest rates if it regularly borrows money to spend. Clearly governments need to get less funds by borrowing and more by taxing the rich.

Sweden urges parents to put limits on snoop phones [Richard Stallman's Political Notes]

Sweden urges parents to put limits on when and where they use snoop phones, especially when around children, because it seems that seeing adults use them is a bad influence.

Clean water to fight antimicrobial resistance [Richard Stallman's Political Notes]

*The world needs clean water to help fight antimicrobial resistance.*

Rich people resist paying for everyone to have clean water, but the result may be the death of some of them as well as many others.

*Antibiotics use in livestock could rise by a third in next 15 years, UN report warns.*

If that happens it will drive antibiotic resistance up. Efforts to reduce the mass use of antibiotics in cattle have met with opposition from Big Ag, which profits from the practice although it results in the death of humans.

The article bizarrely speaks of "human resistance", but the resistance in question is resistance of bacteria to medicines meant to kill them.

(satire) White House doctor assessment of corrupter [Richard Stallman's Political Notes]

(satire) *White House Doctor Claims [the corrupter] A Perfectly Healthy 9-Foot-Tall 35-Year Old.*

Scott Pelley fired for condemning CBS management [Richard Stallman's Political Notes]

Scott Pelley condemned the magat management of CBS for "murdering 60 Minutes", and they fired him for that, as he must have expected. Since then, he has reported that they had tried to command him to insert lies into the show.

Australia's national disability insurance proposed overhaul [Richard Stallman's Political Notes]

*[Australia's] national disability insurance scheme’s proposed overhaul will cause "material harm" to Australians with disabilities, undermine its original intentions and hand unprecedented power to the health minister, the federal government's own reform advisory committee warns.*

In a country where business has political power, they lobby to modify every system and every new law is that the rich and the businesses get the benefit. It seems that they did that to this reform, which was apparently intended to help disabled people. The lobbyists tend to argue that "this is the best outcome that is politically possible."

Wrecker fired independent board for NSF [Richard Stallman's Political Notes]

The wrecker fired the independent board that oversees the National Science Foundation and replaced them with obedient saboteurs. Their first act of sabotage is to terminate the Ocean Observatories Initiative and reserve its monitoring equipment.

Nothing can help the businesses that want to cause mayhem in the ocean like eliminating the equipment that can monitor their activities and the changes they cause.

Iranian regime starting to allow internet use again [Richard Stallman's Political Notes]

The Iranian regime is starting to allow people to use the internet again, but people are worried that the shutdown was used to introduce new systems of surveillance and censorship that are not directly visible.

Oil pipeline across Bosnia [Richard Stallman's Political Notes]

A company lacking in experience has been contracted to build an oil pipeline across Bosnia. It may have been chosen because participants in the corrupter's Jan 6 coup attempt are involved in it.

An inexperienced company is likely to screw up. With an oil pipeline, that could mean oil leaks and ineradicable pollution. But the corrupter and his friends well suppose they will never be held accountable for whatever damage may follow from the choice to be careless.

Probably the Last Back Deck Construction Update [Whatever]

It’s done and the new deck furniture arrived today. The furniture, like the deck itself, is made of a composite material that is designed handle all the heat/cold/sun stresses of outdoor life, and comes with a lifetime warranty, which means its likely to outlive me at this point.

We broke it in by having lunch outside at the main table, and you know what? It was pretty darn nice. I also brought my laptop out to the main table to see how it was for getting work done, and that was pretty pleasant as well. It’s possible, on nicer days, that I might just work outside now. It helps that the deck now has a roof, which makes it easier to see the laptop screen, and a fan, so on warmer days there will be a breeze.

This also means that for the first time in months, we’re pretty much done with having contractors wandering around that house. We have a few minor things that need touching up, but those are things that can be done in hours, not days or weeks. We have our place back! And that’s a lovely thing.

— JS

23:28

Link [Scripting News]

Om Malik died. A longtime friend, most generous kind person in Silicon Valley. It's that time of life. Much love to you brother.

Link [Scripting News]

There’s more to freedom for users than open source. We need fluid unobstructed movement of our ideas. Interop between networks, the same basic idea that created the internet, and that has kept podcasting unowned for 22 years. I am going to ship a textcasting social network soon. It will be open source in new ways made possible by AI.

22:28

21:49

Back In Town [QC RSS v2]

Hey we're back! Sorry for the long period of dead website. Turns out getting your shit hacked and deleted and then being jerked around by your hosting company for weeks is a HUGE pain in the ass. Hopefully that is all behind us now. Thanks for your patience.

Moray Comes Clean [QC RSS v2]

when Momray said "Cubetown messes up sometimes" she specifically meant Mooby

Marten's Gambit [QC RSS v2]

quick make something explode!!

Working On It [QC RSS v2]

they'll get it eventually I'm sure

They're Such Good Friends [QC RSS v2]

the prisoner's dilemma (how much sugar to put in coffee)

Getting A Read [QC RSS v2]

mmm coffee

Scolopendrophobia [QC RSS v2]

Roko has so many embarrassing stories

They Keep In Touch [QC RSS v2]

these two...

Parental Approval [QC RSS v2]

now she gets wifi

One Must Imagine Claire Happy [QC RSS v2]

Moray 22 got squished by a particularly florid metaphor

Friends To Rivals [QC RSS v2]

Two coffee makers AND a trap door

Pet Name [QC RSS v2]

M O O B Y

Heavy Metals [QC RSS v2]

better than the actinides, anyway

Blob Eat Blob [QC RSS v2]

only the strongest shall survive

Or A Boson [QC RSS v2]

or a boatswain

Moray Is Competent [QC RSS v2]

good job Moray

Walking The Plank [QC RSS v2]

the plank at Cubetown is 400 meters long, sentient, and horny

Marsupial Supremacy [QC RSS v2]

Moray could lay an egg like a monotreme if she wanted

Job Talk [QC RSS v2]

Don't worry she's fine

Seabreeze No! [QC RSS v2]

a thousand beaks, a million talons, ten billion eyes. RIP Ms. Beakman, you beautiful bird

In The "Flesh" [QC RSS v2]

stretchy friend...

Gone But Not Forgotten [QC RSS v2]

Emily is my wife's favourite character so this story is basically a little present for her (and possibly...for you???)

Trap Sprung [QC RSS v2]

psst if you sign up for the $5/month tier on my patreon you can see the (very nsfw) thirst pic

Couldn't Be THAT Bad [QC RSS v2]

oh no babby Anh :(

Incremental Progress [QC RSS v2]

the second generation Moray units smelled like a Red Lobster dumpster

Good At Everything [QC RSS v2]

what CAN'T she do

The Shape Of You [QC RSS v2]

At first I was like "is an Ed Sheeran reference going to make this comic seem dated" but then remembered Ed Sheeran's music sucks no matter what year it is

Topical Application [QC RSS v2]

Moray is safety conscious

Bubbles [QC RSS v2]

not THAT bubbles

Get In The Tank, Liz [QC RSS v2]

or Moray will have to do it again

Into The Drink [QC RSS v2]

something's fishy

Medalists [QC RSS v2]

well SOMEONE has to keep her in check

Olympic Games [QC RSS v2]

About that...

Hum And Buzz [QC RSS v2]

might be a digestive issue

Feeds

FeedRSSLast fetchedNext fetched after
@ASmartBear XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
a bag of four grapes XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Ansible XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
Bad Science XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Black Doggerel XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
Blog - Official site of Stephen Fry XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Charlie Brooker | The Guardian XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Charlie's Diary XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Chasing the Sunset - Comics Only XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Coding Horror XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
Comics Archive - Spinnyverse XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
Cory Doctorow's craphound.com XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Cory Doctorow, Author at Boing Boing XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
Ctrl+Alt+Del Comic XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Cyberunions XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
David Mitchell | The Guardian XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
Deeplinks XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
Diesel Sweeties webcomic by rstevens XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
Dilbert XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Dork Tower XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Economics from the Top Down XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
Edmund Finney's Quest to Find the Meaning of Life XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
EFF Action Center XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
Enspiral Tales - Medium XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Events XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Falkvinge on Liberty XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Flipside XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Flipside XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Free software jobs XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
Full Frontal Nerdity by Aaron Williams XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
General Protection Fault: Comic Updates XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
George Monbiot XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
Girl Genius XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
Groklaw XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Grrl Power XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Hackney Anarchist Group XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Hackney Solidarity Network XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
http://blog.llvm.org/feeds/posts/default XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
http://calendar.google.com/calendar/feeds/q7s5o02sj8hcam52hutbcofoo4%40group.calendar.google.com/public/basic XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
http://dynamic.boingboing.net/cgi-bin/mt/mt-cp.cgi?__mode=feed&_type=posts&blog_id=1&id=1 XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
http://eng.anarchoblogs.org/feed/atom/ XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
http://feed43.com/3874015735218037.xml XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
http://flatearthnews.net/flatearthnews.net/blogfeed XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
http://fulltextrssfeed.com/ XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
http://london.indymedia.org/articles.rss XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
http://pipes.yahoo.com/pipes/pipe.run?_id=ad0530218c055aa302f7e0e84d5d6515&amp;_render=rss XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
http://planet.gridpp.ac.uk/atom.xml XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
http://shirky.com/weblog/feed/atom/ XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
http://thecommune.co.uk/feed/ XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
http://theness.com/roguesgallery/feed/ XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
http://www.airshipentertainment.com/buck/buckcomic/buck.rss XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
http://www.airshipentertainment.com/growf/growfcomic/growf.rss XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
http://www.airshipentertainment.com/myth/mythcomic/myth.rss XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
http://www.baen.com/baenebooks XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
http://www.feedsapi.com/makefulltextfeed.php?url=http%3A%2F%2Fwww.somethingpositive.net%2Fsp.xml&what=auto&key=&max=7&links=preserve&exc=&privacy=I+accept XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
http://www.godhatesastronauts.com/feed/ XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
http://www.tinycat.co.uk/feed/ XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
https://anarchism.pageabode.com/blogs/anarcho/feed/ XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
https://broodhollow.krisstraub.comfeed/ XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
https://debian-administration.org/atom.xml XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
https://elitetheatre.org/ XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
https://feeds.feedburner.com/Starslip XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
https://feeds2.feedburner.com/GeekEtiquette?format=xml XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
https://hackbloc.org/rss.xml XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
https://kajafoglio.livejournal.com/data/atom/ XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
https://philfoglio.livejournal.com/data/atom/ XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
https://pixietrixcomix.com/eerie-cutiescomic.rss XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
https://pixietrixcomix.com/menage-a-3/comic.rss XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
https://propertyistheft.wordpress.com/feed/ XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
https://requiem.seraph-inn.com/updates.rss XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
https://studiofoglio.livejournal.com/data/atom/ XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
https://thecommandline.net/feed/ XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
https://torrentfreak.com/subscriptions/ XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
https://web.randi.org/?format=feed&type=rss XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
https://www.dcscience.net/feed/medium.co XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
https://www.DropCatch.com/domain/steampunkmagazine.com XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
https://www.DropCatch.com/domain/ubuntuweblogs.org XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
https://www.DropCatch.com/redirect/?domain=DyingAlone.net XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
https://www.freedompress.org.uk:443/news/feed/ XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
https://www.goblinscomic.com/category/comics/feed/ XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
https://www.loomio.com/blog/feed/ XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
https://www.newstatesman.com/feeds/blogs/laurie-penny.rss XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
https://www.patreon.com/graveyardgreg/posts/comic.rss XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
https://www.rightmove.co.uk/rss/property-for-sale/find.html?locationIdentifier=REGION^876&maxPrice=240000&minBedrooms=2&displayPropertyType=houses&oldDisplayPropertyType=houses&primaryDisplayPropertyType=houses&oldPrimaryDisplayPropertyType=houses&numberOfPropertiesPerPage=24 XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
https://x.com/statuses/user_timeline/22724360.rss XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
Humble Bundle Blog XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
I, Cringely XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Irregular Webcomic! XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
Joel on Software XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
Judith Proctor's Journal XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
Krebs on Security XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
Lambda the Ultimate - Programming Languages Weblog XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
Looking For Group XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
LWN.net XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
Mimi and Eunice XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Neil Gaiman's Journal XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
Nina Paley XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
O Abnormal – Scifi/Fantasy Artist XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Oglaf! -- Comics. Often dirty. XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Oh Joy Sex Toy XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
Order of the Stick XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
Original Fiction Archives - Reactor XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
OSnews XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Paul Graham: Unofficial RSS Feed XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Penny Arcade XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Penny Red XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
PHD Comics XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Phil's blog XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
Planet Debian XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Planet GNU XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
Planet Lisp XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Pluralistic: Daily links from Cory Doctorow XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
PS238 by Aaron Williams XML 17:21, Sunday, 28 June 18:09, Sunday, 28 June
QC RSS v2 XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
Radar XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
RevK®'s ramblings XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
Richard Stallman's Political Notes XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Scenes From A Multiverse XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
Schneier on Security XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
SCHNEWS.ORG.UK XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
Scripting News XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Seth's Blog XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
Skin Horse XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Tales From the Riverbank XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
The Adventures of Dr. McNinja XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
The Bumpycat sat on the mat XML 17:28, Sunday, 28 June 18:08, Sunday, 28 June
The Daily WTF XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
The Monochrome Mob XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
The Non-Adventures of Wonderella XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
The Old New Thing XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
The Open Source Grid Engine Blog XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
The Stranger XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
towerhamletsalarm XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
Twokinds XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
UK Indymedia Features XML 17:28, Sunday, 28 June 18:10, Sunday, 28 June
Uploads from ne11y XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
Uploads from piasladic XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June
Use Sword on Monster XML 18:07, Sunday, 28 June 18:54, Sunday, 28 June
Wayward Sons: Legends - Sci-Fi Full Page Webcomic - Updates Daily XML 17:35, Sunday, 28 June 18:21, Sunday, 28 June
what if? XML 17:35, Sunday, 28 June 18:16, Sunday, 28 June
Whatever XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
Whitechapel Anarchist Group XML 17:49, Sunday, 28 June 18:38, Sunday, 28 June
WIL WHEATON dot NET XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
wish XML 18:07, Sunday, 28 June 18:52, Sunday, 28 June
Writing the Bright Fantastic XML 18:07, Sunday, 28 June 18:51, Sunday, 28 June
xkcd.com XML 17:42, Sunday, 28 June 18:25, Sunday, 28 June