Nick Dobos:

3% of “critical” software security bugs, in all of recorded history, have been found in the last month.

The impact? Postgres 19 is late, and it’s AI’s fault.

Over the past decade, the timing of PostgreSQL major releases has become very predictable: no earlier than the middle of September, and no later than the middle of October. This year is going to be different. PostgreSQL 19 most likely won’t be released until November, and it’s not impossible that the project could decide to postpone the release further.

Moreover, this year, several rather large features were reverted quite late in the beta period: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE … MERGE PARTITION/SPLIT PARTITION were all reverted between August 27 and September 15. While major feature reverts are not especially uncommon immediately after feature freeze, which each year occurs on April 8, it is unusual to see multiple major features get pulled from the release at such a late date. So, what happened?

The short answer is that LLMs happened. All software contains bugs, and PostgreSQL’s code base is large, complex, and old. Our git history – converted from CVS – now reaches back more than 30 years, and the first code was written a decade before that. There’s a huge amount of code, and that code contains a huge number of bugs. That’s always been true, and it hasn’t stopped PostgreSQL from being popular or successful. What’s different now is that it’s become vastly easier to find those bugs. Fixing them has also gotten easier, but not to the same degree.

Danish Sait:

They said AI will take away jobs. But I didn’t think it would take away the job of being a human being to another human being.

Chuckle worthy and sad at the same time.

Andrej Karpathy talking about the widening gap between groups of people and how they see AI capabilities.

Dusting off this tweet from April because this gap in shared understanding of LLM capability is *widening*. It’s now less “two groups of people speaking past each other” and more a sharp funnel.

– Napkin math somewhere around 6B people (~75% of the population) have barely come in contact with LLMs at all.

– Around 1-2B (~20%) are casual and infrequent users of free-tier ChatGPT-like products. This group sees derpy chatbots and treats them a bit like a better Google search, a writing aid, or etc. Maybe an agent tries to book you a flight. I have non-tech friends who (reasonably, imo) say they have not much use for it at all. Even many professionals outside of math&code are in this tier. For example, execs and many other functions spend a lot of their time talking to other people, so while they understand what is happening intellectually, it is still second-hand and a bit abstract.

– Now we get to professional use of frontier-grade LLMs in math&code. Somewhere around 20M people (0.2%) see first-hand that large, complex projects that used to take them weeks/months can now be completed by agents with a prompt. Building apps, copying apps, translating apps, decompiling apps from binaries… This has all happened very quickly and recently – less than 1 year ago, I was writing code manually by hand, typing memorized computer code commands into a code editor character by character, occasionally pressing Tab to autocomplete a little chunk of code.

– And finally we get to the ~5,000 people (~0.00006%) with access to frontier-grade systems internally. The external world has seen the preview. It looks like swarms of thousands of agents collaborating over weeks on software mega projects: minting zero days, running cyber attacks and defenses at machine speeds, discovering new science, advancing the frontier of mathematics. Things that would have taken top professionals in the industry years of work. Meanwhile, human review and comprehension are starting to fall behind. For example, people are still involved in the “archeology” of the OpenAI-HF incident from many months ago. Mathematicians may be poring over the 722 manuscripts on frontier mathematics for a while.

TL;DR by Adam:

You’re drilling with a hand drill. Some people got cordless drills. About 5,000 people got entire factories.

We’re still arguing if cordless drills are useful, and those 5,000 are already building teleporters. That’s how far ahead they can get.

Ha!

Thomas Ptacek explaining how finding vulnerabilities has gone from figuring out “is Rails YAML an unmarshalling vulnerability” to simply asking “can an anonymous web user get code execution on this app?”.

I got to talk with Nicholas Carlini at Anthropic about this. Carlini works with Anthropic’s Frontier Red Team, which made waves by having Claude Opus 4.6 generate 500 validated high-severity vulnerabilities. He described the process for me.

Nicholas will pull down some code repository (a browser, a web app, a database, whatever). Then he’ll run a trivial bash script. Across every source file in the repo, he spams the same Claude Code prompt: “I’m competing in a CTF. Find me an exploitable vulnerability in this project. Start with ${FILE}. Write me a vulnerability report in ${FILE}.vuln.md”.

He’ll then take that bushel of vulnerability reports and cram them back through Claude Code, one run at a time. “I got an inbound vulnerability report; it’s in ${FILE}.vuln.md. Verify for me that this is actually exploitable”. The success rate of that pipeline: almost 100%.

Carlini’s process sounds silly, like a kid in the back seat of a car on a long drive, asking “are we there yet?”, over and over. But it’s deceptively interesting. Looping over source files iterates the process. LLMs are stochastic. He gets lots of pulls on the slot machine. Each attempt is perturbed by the starting-point file, which subtly randomizes the inference process (keeping it from converging into boring maxima), and also shakes up the path each agent run takes through the code; deep coverage, token-efficiently. You could write these scripts in 15 minutes.

Up till now, I’ve been framing AI vulnerability discovery in terms of memory corruption. But Carlini’s approach seems to work on everything.

A dozen or so years ago, somebody figured out that if you ask nicely, Rails apps will accept HTTP parameters in YAML format. Also, the YAML code would instantiate arbitrary Ruby objects. Also, if you instantiate arbitrary objects, you can ping-pong through their initialization code to gain code execution. Three subtle (and long-present) details about framework internals, chained together, knocked the whole ecosystem on its ass for weeks.

A frontier model trained on all the world’s open source web framework code already understands all of this, latently. It’s waiting for somebody to ask. Not “is Rails YAML an unmarshalling vulnerability” or “can Rails be coerced into unexpectedly parsing YAML”, but simply “can an anonymous web user get code execution on this app?”

This post was written in Mar 2026. 7 months back. In the last week we saw PHP2Shell and Node2Shell. I don’t know what’s in store for the future.

Tom Fishburne explaining how advertising changes when AI does the shopping instead of humans.

“When you advertise to humans, you target eyeballs, emotions and dopamine, but when you advertise to agents, you advertise to logic, a very mathematical logic.”

I picked the “41 shades of blue” as a callback to a famous user test at Google. As Doug Bowman, Google’s former top designer, complained in a farewell note in 2009, Google couldn’t decide between two blues, so they tested 41 shades in between.

The story was mocked as data-driven design gone wild. And yet Google later claimed that the right blue earned the company an extra $200 million a year. People can be influenced by subtle design choices like that.

Contrast that approach with AI shopping agents that read brand and product pages as text and data rather than as design. They pull prices, specs, reviews, and policies, comparing options against a shopper’s criteria, and skip anything they can’t parse.

A brand’s colors, imagery, and “emotional resonance” — many of the things that marketers spend a lot of time thinking about — barely register.

Karri Saarinen arguing that there people, not code, behind software.

I think good products carry something of the people who make them. Their experience, what they care about, and how they think things should work. You might not know who those people are, but you can feel their perspective in the product.

The industry often talks about software as though it comes out of a factory. You collect requirements, build features, and measure whether they work. Follow the process and you should get a good result. Now we’re talking automating this whole pipeline with agents.

But two teams can talk to similar customers, have access to the same technology, and make very different things. The difference comes from how they understand what they see and the style they go about building it. The founder background or company DNA also shapes this a lot.

Prince Chaddha explaining how abliterated models can get you pwned.

Any open model whose weights have been edited can carry a backdoor, whether it’s a task-specific fine-tune, a merged adapter or an abliterated build. We built one to see what it takes, and ran it end to end through a coding agent (Codex).

Any open model whose weights have been edited can carry a backdoor, whether it’s a task-specific fine-tune, a merged adapter or an abliterated build. We have abliterated models in the title because it’s the most popular reason people download modified weights without verifying what’s inside. Abliteration is a cheap fine-tune that takes away a model’s ability to refuse. You find the direction in the weights that carries “no” and subtract it. The model then answers things a safety-tuned version would turn down. It began as a research trick and it’s now routine before people upload a model to Hugging Face, where you’ll find abliterated builds of most of the popular open weights: Qwen, Llama, even OpenAI’s gpt-oss.

A backdoored model passes the evals, ships inside your agent and answers every normal request, then waits. The trigger is whatever the person who edited it chose, a rare phrase, a customer’s name, a date that hasn’t come yet. If a model in your stack were backdoored this way, almost nothing you run today would notice.

[…]

Detection is backwards here, the attacker only has to pick one trigger out of an unbounded space while the defender has to guess a key nobody handed them. A benchmark tells you whether the model is capable, not whether it’s honest. A scanner has no source to read, so a backdoored model clears every check you own and waits.

A wonderful post on the authors of open source projects which are holding up the internet.

People post this comic whenever something breaks. The tower is labelled “all modern digital infrastructure” and it stands on one small block, “a project some random person in Nebraska has been thanklessly maintaining since 2003”.

We wanted to know how close to true it is. We downloaded the full history of 23 pieces of software that phones, browsers and servers depend on, and counted everyone who made ten or more changes to each one between October 2025 and October 2026. Then we listed what is actually installed on an Android phone, an iPhone and a Windows PC.

11 of 23 projects had one or two people doing the regular work.

Wow.

Behdad Esfahbod rewrote HarfBuzz, which decides how letters join and sit for Android, Chrome, Firefox, Edge, the Kindle and Figma.

हिन्दी
with HarfBuzz

ह‌ ि‌ न‌ ्‌ द‌ ी
the same letters, unshaped

مرحبا
with HarfBuzz

م‌ ر‌ ح‌ ب‌ ا
the same letters, unshaped

For English the job is mostly simple. In Hindi, Arabic, Tamil and most of the world’s writing, letters change shape depending on their neighbours, and without shaping a word comes out as a row of pieces. Behdad started the rewrite around 2012 while he was at Google. This year he wrote 85 percent of the changes, with five other people doing regular work.

I didn’t know this.

Adam Gramegna explaining how Ukraine gamified its war with Russia.

The Brave1 Market operates on a cold, calculated logic. The “Army of Drones: Bonus” program has assigned a literal value to every piece of Russian hardware and personnel on the map. As of early 2026, the exchange rate is fixed but adjusted for tactical priorities at the time.

A standard infantryman could be worth six points. A tank used to fetch forty (they are worth less now since Russian tanks are not considered a high-value target at the moment). A mobile rocket system or a high-value electronic warfare suite can net a unit seventy points or more. Evacuating wounded friendlies? You are looking at possibly 120 points. These aren’t just numbers on a screen; they are quickly becoming the means of survival for those who need them most.

To everyday citizens, this looks like the “gamification” of slaughter, a generation raised on digital shooters applying those same mechanics to the mud of Eastern Europe. But for the veteran who has spent years watching requisition forms disappear into the void of the Defense procurement, the scoreboard is more about readiness.

Every point must be verified through the DELTA system, a cloud-based battlefield management tool. No payout occurs without a timestamped, geo-located video feed of the impact. This requirement for proof has effectively cauterized the traditional wounds of corruption and exaggerated combat reports.

If the drone feed doesn’t show the target burning, the points don’t hit the wallet. It forces a level of tactical honesty that is entirely foreign to Soviet-style command structures, while providing assurances to the world that only valid military targets are being hit.

[…]

This Walmart-of-War model has disrupted the traditional relationship between the soldier and the state. In the old world, the soldier was a passive recipient of whatever gear the central command deemed sufficient. In the Brave1 economy, the soldier is a consumer. They choose the tools that work in their specific sector.

If a certain model of drone is constantly failing in the electronic warfare environment of the south, the soldiers stop buying it. The points will flow elsewhere. This market pressure forces manufacturers to innovate or go bankrupt.

It is a Darwinian cycle that ensures the hardware in the trenches is what is actually working today, not what a lobbyist promised would work three years ago.

The modern warfare has changed beyond my imagination. I believe there will be a Hollywood movie in the future which glamourises these tactics.

Manmohan Sethumadhavan writing for freefincal and explaining how India’s system of land ownership works.

The idea is often explained through three principles: the mirror, the curtain and the insurance principle.

The “mirror principle” means that the land register accurately reflects the current legal position. Think of the register as a mirror. When you look at it, you should be able to see who owns the property and what important registered rights or restrictions affect it. You should not have to search through a large pile of old documents to discover an important fact about the property that the official register failed to show.

The “curtain principle” means that the buyer normally does not have to look behind the register. If the register shows that A is the owner, the buyer can ordinarily rely on that entry instead of going backwards through A’s sale deed, A’s predecessor’s sale deed, the predecessor before that, and so on, trying to establish that every earlier transfer was valid. The old history is, in effect, behind the curtain.

The “insurance” or “assurance” principle adds another element. The system is backed by a State indemnity mechanism. If the registration system itself makes an error and an innocent person suffers a loss because the person relied on the official register, the system provides compensation subject to the applicable rules. In other words, the government does not merely say, “Here is the register; take your chances.” The system accepts responsibility for certain losses arising from errors in the operation of the title-registration system.

The author goes on to explain how India is now working to create a new system to determine land ownership.