*Interior Secretary's Calendars Dominated by Big Oil and Big Tech, Analysis Finds.*
More effective ways to extract CO2 from the air than doing it mechanically and storing it in underground spaces.
The UK government is going to extremes of repression in trying to prevent talks — even remote ones — by people who criticize violence — specifically, Israel's violence against Palestinians, and oil companies' violence against civilization and the natural world.
*The Home Office tried to cancel a pro-Palestine event here in Hackney. Labour's petty authoritarianism has gone too far.*
Meanwhile, the perpetrators are treated with utmost consideration.
*Australia sanctions individuals and company involved in illegal West Bank settlements.*
All countries have a duty to do this.
The minister in charge directly stated that all Israeli settlements in Palestinian territory violate international law. That removes my uncertainty over whether Australia officially recognized this.
*Russia, Saudi Arabia and Australia are the three biggest exporters of [future] carbon dioxide in history, according to analysis of fossil fuels since 1850.*
US citizens: call on Congress to Pass the Sanders-AOC Ban Flock Act to counter mass surveillance!
We need more than this. To access the recordings of surveillance cameras should require a warrant. But this is a start.
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.
US citizens: call on the Senate to stand firm for the crackdown on Pentagon contractor profiteering.
See the instructions for how to sign this letter campaign without running any nonfree JavaScript code--not trivial, but not hard.
US citizens: call on Congress to cut off the funds for war with Iran.
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.
US citizens: call on Congress to fully fund public education.
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.
US citizens: call on Congress to Impeach Secretary Markwayne Mullin of the Department of Hatred and Savagery.
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.
I would like to know how to downmix 7.1 audio to stereo without it sounding like hammered dogshit. Specifically in the context of Scott Pilgrim, which we are screening at DNA Lounge this Sunday.
The file I have is 1:52:15, 1920x1040, 7.1 aac 48kHz. Here are the things that I have tried that sound terrible:
ffmpeg='ffmpeg -hide_banner -loglevel error -y -ss 1:01:33 -i pilgrim.mkv -t 90 -map 0:v:0 -map 0:a:0 -vcodec copy -acodec aac -b:a 192k -movflags faststart' $ffmpeg -ac 2 pilgrim-ac2.mp4 $ffmpeg -ac 2 -lfe_mix_level 1 pilgrim-ac2-lfe.mp4 $ffmpeg -af 'pan=stereo| FL < 0.274804*FC + 0.388631*FL + 0.336565*SL + 0.194316*SR + 0.336565*BL + 0.194316*BR + 0.274804*LFE | FR < 0.274804*FC + 0.388631*FR + 0.336565*SR + 0.194316*SL + 0.336565*BR + 0.194316*BL + 0.274804*LFE' \ pilgrim-pan.mp4 # (via this and this)
Also doesn't work: importing the 7.1 file into iMovie directly. That sounds just like "-ac 2" but with extra clicks.
What did work was having Gabe use Adobe Audition to dump out a 2ch WAV. So we have a solution for this Sunday. But I would still like to know how to solve this in the future using normal tools.
If you are about to "Why don't you just"...
- ...play the 7.1 file:
my nightclub is stereo. - ...play the 7.1 file and hope for the best in QuickTime Player or VLC downcoding it in realtime:
I need to do some editing on the file (adding pre-roll and intermission) and I use iMovie for that, which is stereo. - ...use something besides iMovie to edit video:
I do not like iMovie but I understand it. Any time I have experimented with something besides iMovie, I have both not liked it and not understood it. - If you are about to say, "I haven't tried this, but..." please don't. I have a very specific test case up there. Run those three recipes on that file. Listen to them. If your fourth recipe sounds better, then and only then tell me about it.
If you maintain an open-source project right now, your pull request queue probably looks very different than it did two years ago.
I maintain SwiftTerm, an open-source terminal emulator library that is now seven years old. Today, I estimate that about 80% of the pull requests I receive involve AI in some capacity. Looking back, though, this didn't happen all at once—it came in distinct waves.
Disclosure: as a Mexican national that routinely writes tedious and typo-ridden English blog posts, I had Antigravity fix my writing and repeated tedious and repetitive points (as my wife often points out).
Wave One: Vibe-Coded Band-Aids and Fork Experiments
Before people even started opening AI-assisted pull requests on my repository, I would browse the GitHub network graph just to see what forks were popping up and what problems users were struggling with. Early on, what I found was a lot of "vibe coding"—folks patching around issues in ways that were fundamentally wrong, slapping surface-level band-aids over deeper terminal state bugs. I would fix or implement the feature, despite the fact that the user had not submitted the fix - for the sake of helping all my users.
In one fork I stumbled across, someone had clearly unleashed an autonomous agent to try to fix all of my open issues in rapid fire. Luckily, they never actually submitted those PRs—they were likely just experimenting—and it was only my nosy self browsing the network graph that spotted it. Still, looking through those commits confirmed the early reality: the fixes weren't worth merging. They solved surface symptoms without understanding the system.
The Rise of the Promptsplainer
Alongside those early waves came a new open-source archetype—one that many communities had to deal with: the Promptsplainer.
Some folks are really eager to particiapte in improving a project and LLMs have opened new doors, but they lack some basic etiquette.
A Promptsplainer is someone who asks an LLM a question, gets back a confident-sounding explanation or a sprawling patch, and suddenly believes they can override decades of hard-won domain expertise. They don't actually understand the underlying quirks, race conditions, or protocol edge cases of the codebase they are touching. When a veteran maintainer points out a flaw, the Promptsplainer doesn't go investigate the code; they just copy-paste the maintainer's review comments straight back into their chat session and paste whatever the bot spits out next.
You don't need a massive daily flood of Promptsplainers to feel the damage. Even the occasional encounter can fill a maintainer with rage - and with good reason.
Wave Two: "Send a Patch" Finally Became Real
Here is what has changed dramatically over the last year. We went from AI fixes being flat-out wrong or lazy band-aids to pretty much landing in the right ballpark.
To appreciate why this matters so much to me, you have to remember what maintaining an open-source library looked like just a few years ago. Back then, I would get a steady stream of bug reports—and if I had the spare time, the patience, the kids went to sleep early, and my Netflix queue was empty, I might actually sit down and fix the bug.
For decades, open-source communities had a semi-joking, semi-exasperated stock response whenever a user asked, "Why doesn't it...?". We told them, "Patches welcome," or "Send a PR." Most of the time, we knew they wouldn't, because diving into a complex codebase from scratch was too steep a climb. The perfect storm between unpaid volunteer work, uneducated takes and exasperation.
Like many others, I have witnessed the change from getting bug reports to getting detailed pull requests. And I am personally grateful for this.
My philosophy on incoming contributions comes down to a simple reality: every PR represents a real pain point caught in the wild. It means a real user ran into a problem in their day-to-day work, reported or tracked down the issue, found a working solution, and felt the pain acutely enough that they took the time to package it up and upstream it.
As a maintainer, that is an infinitely better signal than my own laundry list of wish-list items sitting in the issue tracker. Even if the implementation needs additional work, someone just handed me proof of a real-world problem along with a concrete starting point to fix it.
Multi-Agent Code Review on My Side of the Table
The catch is that many coding models and agents still have a bad habit of just doing the fix—taking the shortest path to make a test pass without stepping back to look at the whole library. And not every contributor has learned how to tune their agents for deep engineering review, or has access to the best models for it.
The first pass of AI-generated code often needs work, and that is okay. Just as we spent years developing the discipline to master our programming languages, debuggers, and in some cases, write m4 macros, we now need to develop the muscle for using AI tools effectively—learning how to steer them, verify their assumptions, and audit their output.
For me, building that muscle meant putting AI on my side of the table to bridge the gap. Before I even bother reading a contributor's patch line-by-line, I religiously run /code-review in Claude and /review in ChatGPT [1].
These review passes routinely catch far more than narrow syntax nits—they surface genuine architectural flaws, subtle API breakage, rare side effects, and terminal conformance problems that would take me hours to trace manually [2].
Armed with that feedback, I can point contributors toward concrete architectural fixes—or, if someone disappears after opening a PR for a critical bug, I can clean up their branch and land it myself.
Some maintainers lament that reviewing these PRs feels like talking to someone who just copies and pastes feedback into a remote LLM. But we are still communicating with a human being on the other end. That gives us a real opportunity not just to coach contributors on how to use these tools responsibly, but to model and adopt better engineering practices across our industry. Given that the economics of top-tier reasoning models aren't ideal for everyone doing casual open-source work, I’m happy to foot that bill on my end for the sake of keeping my library healthy.
The Friction of One-Size-Fits-All Rules
This brings me to why I’ve been watching the broader debate around AI policies in large projects like Gnome and Godot with a lot of sympathy—and a bit of concern.
At Godot's massive scale, protecting volunteer reviewers from unvetted submissions and the occasional Promptsplainer is a completely understandable instinct. Nobody wants their Netflix time eaten up by drive-by code the author didn't bother to understand.
The challenge is that drawing hard lines around how code was written inevitably creates friction for experienced contributors who are already doing the architectural heavy lifting. Recently, I tried to upstream a small, production-tested bug fix to Godot as a trial balloon—one of roughly 60 to 80 improvements my team has built and tested in our own tree. Because I disclosed my AI workflow honestly, it ran afoul of their strict guidelines and was rejected.
When a policy polices provenance rather than quality, two unintended things happen:
- It penalizes transparency: Honest contributors who disclose their tools get blocked, while others are quietly nudged to keep quiet and pretend they typed every character by hand.
- Good fixes stay locked in private forks: Rather than wrestling with policy friction, teams like mine simply keep useful patches in our own internal trees. Because AI has made maintaining forks trivial, it doesn't slow us down—it just means the broader community misses out on fixes that could have helped everyone.
Accountability Over Provenance
The Promptsplainer is a real headache, and open-source projects are right to push back against uncomprehending, drive-by contributions.
But the antidote isn't banning the tools—it's requiring human accountability paired with better review tooling on the maintainer's side. At the end of the day, as the maintainer of a library, it is my role to make the editorial decisions about what goes in—and the people who depend on my library trust me to make those calls. Whether a patch started in an LLM prompt or was typed out by hand doesn't change that responsibility. If a contributor understands the problem, has tested the fix, and can engage thoughtfully in review as a human being, the models they used in their editor shouldn't disqualify their work.
Of course, scaling that kind of review culture when a handful of core maintainers are already stretched thin is a structural challenge all its own.
[1] With Claude I use Opus 5.5 alongside /review in GPT 6.2 with Sol-xhigh. In Claude, /code-review actually launches multiple distinct agents in parallel, each focused on different goals and common engineering mistakes. Looking forward to Antigravity to get this.
[2] In fact these reviews are so thorough, that I use /code-review on my own changes before shipping. In a seven-year-old codebase, it is impossible to keep every historical invariant in your head at once, and those agents regularly catch edge-case scenarios I had completely forgotten about.

Please enjoy jwz mixtape 261.
Difficulty: impossible.
I'm really enjoying this.
A lot.
(Safari 26.6.1, macOS 14.8.9.)
Los Angeles County health officials are ordering the operators of the troubled Chiquita Canyon Landfill in Castaic, California, to provide hotel accommodations and other emergency assistance to nearby residents after a violent eruption sent a towering geyser of decomposing garbage and methane gas into the air Monday afternoon. [...]
"They were drilling this hole about 150 feet deep and 3 feet wide down into this mound of trash," Los Angeles County Fire Capt. Aaron Katon said. [...] Investigators said workers drilling into the landfill apparently encountered a pressurized pocket of methane, causing material to erupt from the opening.
Previously, previously, previously, previously, previously, previously, previously, previously, previously, previously.
Detroit transit officials say two horses that boarded a city bus Saturday appear to have been brought aboard for reasons other than service, and they called the incident an opportunity to retrain bus operators. [...] The department said it welcomes service animals that meet the requirements of the Americans with Disabilities Act.
It turns out Jordan Williams wasn't actually trying to ride a Detroit bus with his horse Raven:
Williams, cofounder of Urban City Cowboys, was out with his best friend (another horse owner), and their horses in Detroit over the weekend for a fundraiser, riding along 7 Mile Road, when he came across a Detroit Department of Transportation (DDOT) bus pulling into a stop.
Williams said he spoke to the driver, jokingly remarked that the horse was his service animal and was on and off the bus in no time, much to the astonishment of a passenger inside who snapped some pictures. Williams didn't know the person outside recording him -- a video that would soon go viral -- but he did intend to make a splash with the stunt.
Previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously.
Update: I spoke too soon.
The leaf blower guy is here.
It is actively raining, and the smattering of leaves that exist in the concrete slab of a neighborhood that I call home are stuck to the sidewalk, utterly impervious to blowing action.
But I guess my HOA is paying him to do this, so here we are.
Update 2: He went and got a broom! Thus demonstrating that "complete the pointless task without a 90dB compressor on your back" was a technology that had been available to them all along.
This is "Scorpion (2026)" where Beard Man is living a quiet life until The Agency finds him, except this time Aaron Eckhart plays Jason Statham.
I did not expect much from a movie like this, but that expectation dropped to the center of the Earth once the producers demonstrated their utter contempt for visual effects artistry at both the creative level ("we don't value your work") and at the financial level ("and we're definitely not paying you for it").
Even the fake Google Maps displays on their phones were slop, as they crossed the Northern border into "Calyda".
Well, last week I just white-knuckled it and wrote my own from scratch. I call it "Dox". It took about three days to feature-complete, then another day of tweaking. 4k lines of PHP, 250 lines of JS.
Then I had to write a tool to export our nine years of data from Basecamp and into Dox and that took another couple days (surprise, the Basecamp data-export format is comically bad, so I had to roll my own via their API.)
I'm not releasing Dox to the public, because it depends on a few of my internal libraries and I don't feel like spending the time to make it usable for people outside of DNA Lounge, nor do I want to support it for you. At all.
This is just by way of saying: if you find yourself thinking, "This is some bullshit, I should just write my own and be done with it"...
...you might be right.
Planet Debian upstream is hosted by Branchable.



