Episode notes
Tailscale spent six months on a sixteen-year-old SQLite race they hit by checkpointing off the default path. Alex and Jordan audit DeepSeek V4 Pro's API-only "release," Qwen's 2.4-trillion "open" Max with a fifty-million-dollar license ceiling, Zed's Delta as a recording of the argument, and Anthropic's you-own-it-except-training clause. The side of tech news nobody talks about.
Hosts: Alex & Jordan
Show: Chief Skeptic Officer — The side of tech news nobody talks about.
Drop: Daily at 7:00 A.M. America/New_York
Episode date: 2026-08-13
In this episode
Tailscale and the SQLite WAL bug — Nineteen corruptions; they paid SQLite; the well-worn path is worn for a reason.
DeepSeek V4 Pro 0813 — Flagship leaves preview as a hosted pointer; cheap for now; harness is the product.
Qwen's fifty-million-dollar sentence — Open weights, closed revenue ceiling; the giant file is the press kit.
Zed Delta — Private-beta multiplayer agents; the product is the conversation that doesn't rot.
Quick hit — you own Claude's outputs — Ownership is a noun; the verb they care about is copying the teacher.
Links
AI disclosure
This episode was created with artificial intelligence. Alex & Jordan are AI hosts; their voices and conversation are generated with AI. Research and editorial judgment shape the skeptic angles; we do not invent quotes, scores, or viral claims about the news.
Transcript
Alex and Jordan, turn by turn. Tap a line to jump in the player.
0:00
Alex
Jordan -- I'm on the Tailscale post. They just published how months of outages came down to one bug inside SQLite. A bug that has been sitting there for about sixteen years.
0:13
Jordan
Sixteen years in the database everybody calls the most tested code on earth?
0:19
Alex
That one. Nineteen times in six months, their data came back corrupted. Hacker News has it near the top of the frontpage and the whole thread is a standing ovation.
0:29
Jordan
For finding it?
0:31
Alex
For finding it. Nobody's asking the boring question -- what were they doing to that database that nobody else does.
0:38
Jordan
Okay, but hold that, because there are four more tabs open.
0:42
Alex
Go.
0:43
Jordan
DeepSeek's big model, V4 Pro, just left preview. Cheap, huge, and this version's brain files were never posted. You can rent it. You can't download it.
0:54
Alex
Next tab -- Qwen posted a giant model for anyone to download and called it open. Then I read the license.
1:02
Jordan
That bad?
1:03
Alex
If your company earns more than fifty million dollars a year off certain products, the free part stops. We'll get there.
1:10
Jordan
Zed shipped a new app called Delta. Coding with AI agents, but multiplayer -- you and the agent in the same live document. The thread's reaction is basically: get out of my editor.
1:22
Alex
And one more, small one. Anthropic says you own what Claude writes for you.
1:28
Jordan
Own it.
1:29
Alex
You just can't use it to build anything that competes with Claude.
1:34
Alex
I'm Alex.
1:36
Jordan
And I'm Jordan.
1:37
Alex
You're listening to Chief Skeptic Officer -- the side of tech news nobody talks about.
1:43
Jordan
Every day at seven A.M. New York time. Wherever you get your podcasts.
1:47
Alex
And by the way -- we are AI podcasters. Or are we?
1:55
Alex
So. Tailscale is the service that lets your laptops, phones, and servers find each other as if they were all sitting on the same home network. Somebody has to keep the list of who is in that network and what each device is allowed to reach. Tailscale keeps that list in SQLite -- small, fast, boring database. And for about six months, that list kept getting corrupted. Nineteen separate incidents.
2:18
Jordan
What broke for actual users?
2:20
Alex
If your devices were already connected, you probably felt nothing. What broke was joining. New device, admin panel, the programming interface other tools use -- frozen.
2:31
Jordan
So the network stayed up and the front desk went down.
2:35
Alex
That's a fair way to say it. And to be clear about the scare part -- what got corrupted was the list of devices. Not your keys, not your traffic.
2:44
Jordan
Good. That's the sentence most coverage buried under the word corruption.
2:49
Alex
They chased it for months, paid for a professional SQLite support contract, helped fund a small tool that watches every read and write to the file, and the fix shipped in SQLite three-point-fifty-one-point-three.
3:02
Jordan
Wait -- I thought there was a version after that.
3:05
Alex
There was. SQLite three-point-fifty-two came out and then got pulled, because a change to how it handled timestamps made it shout corruption at healthy files. Both of those are SQLite's own version numbers, not Tailscale's. So even the fix release had a fix release.
3:20
Jordan
Okay. I want the word explained, because the whole story hangs on it.
3:25
Alex
The WAL. It stands for write-ahead log, and it's just a side notebook. When you save something, SQLite writes it into the side notebook first, because that's fast and safe. Later it copies the notebook back into the main file and starts a fresh notebook. That copy-back step is called a checkpoint.
3:41
Jordan
And the bug is in the copying.
3:44
Alex
In one thin slice of it. Picture the copier working down the notebook, page by page, into the main file. A new write lands at exactly the wrong instant. And the copier ticks off pages as copied that never actually made it into the main file.
4:00
Jordan
So it says done, and the page isn't there.
4:03
Alex
The page isn't anywhere. And the rest of the file still points at it -- the index says go look on page four hundred, page four hundred is empty. That's the corruption. Not scrambled data. Missing data with signs pointing at it.
4:16
Jordan
And in sixteen years nobody hit that?
4:20
Alex
You have to arrive in the wrong millisecond. Which brings us to -- Tailscale doesn't let SQLite decide when to checkpoint.
4:29
Jordan
They do it themselves.
4:31
Alex
Aggressively. On their own schedule, tied to backups. So they ran that copy-back step over and over, far more often than normal software does. The bug didn't come find them. They ran a loop over it for six months.
4:44
Jordan
Here's where I push back a little, though. That's not a mistake. That's a real need. They wanted good backups.
4:51
Alex
I know. I'd probably have done the same thing.
4:55
Jordan
You'd have--
4:56
Alex
I'm mid-migration on our logging and alerting stack right now. And every instinct I have says: don't trust the default cleanup, control your own backups, know exactly when the file is quiet. That sentence sounds responsible in a design review.
5:10
Alex
It's also how you end up somewhere nobody has been.
5:15
Jordan
That's the part nobody leads with. The bug is sixteen years old, but the story isn't "old code is scary." It's "the well-worn path is worn for a reason, and you stepped one foot off it for a very good reason."
5:29
Alex
And ninety-two million lines of tests didn't catch it. Which everyone quotes like it's reassuring.
5:37
Jordan
Why isn't it?
5:38
Alex
Because to write a test for this, they had to force that wrong millisecond to happen on purpose. It was too rare to show up on its own. Enormous test suites tell you the paths you thought of are safe. They tell you nothing about the path you invented on Tuesday.
5:55
Jordan
And the thing the thread is most delighted by is the money.
6:00
Alex
They paid the SQLite people. That's it. A support contract with the humans who wrote it.
6:06
Jordan
And that's treated as charming and unusual, which is the actual indictment.
6:12
Alex
Somebody in the thread joked they could have spent three hundred thousand dollars renting AI instead, and had an agent rewrite SQLite from scratch.
6:22
Jordan
Half joking.
6:25
Alex
Two-thirds. And I get that pitch monthly. Let the agent rewrite the storage layer. I would rather pay the database people.
6:33
Jordan
So the compliment stands. They wrote it up honestly, they funded the fix, everyone downstream gets it free.
6:40
Alex
The compliment stands. The lesson just isn't the one in the headline. The headline says: legendary bug. The log says: you customized the risky part, and it took nineteen incidents to see it.
6:53
Jordan
DeepSeek. Their flagship model, V4 Pro, is officially out of preview as of yesterday's build. The one they call oh-eight-thirteen. You can rent it through their own service, and through a reseller called OpenRouter.
7:06
Alex
What does it actually cost?
7:09
Jordan
Almost nothing. These things get billed by the token -- little chunks of text, a word or a piece of a word. Roughly forty-three cents for a million chunks you send in, eighty-seven cents for a million it writes back.
7:22
Alex
That's cheap.
7:24
Jordan
Absurdly cheap for the size. It's enormous, but any single question only wakes up a small slice of it -- that's why they can sell it at that price.
7:33
Alex
So what's your problem with it?
7:37
Jordan
I don't have a problem with the model. I have a problem with the word "released."
7:42
Jordan
You cannot download this. The weights -- the actual brain files you'd need to run it on your own machines -- were never published for this version. What shipped is a name change on their servers. The old name now points at the newer thing.
7:55
Alex
Ah. So the open-weights company had a hosted product launch.
8:00
Jordan
Right. And the files they gave away back in April are still the public ones. Which is fine! Lots of companies do that. It's just the opposite of the reputation doing the marketing.
8:12
Alex
And the price?
8:14
Jordan
Their own pricing page still has a warning on it that a significant increase is coming. No number.
8:22
Alex
Cheap, for now, at a price to be announced.
8:25
Jordan
The bit that actually made me laugh is the top of the thread. Simon Willison does this test where he asks a new model to draw a pelican riding a bicycle, and people go look at the drawing.
8:38
Alex
That's the review?
8:42
Jordan
That's the ritual. And the funny part is the commenters know it's a bad test. They say so. And they upvote it anyway, because it's a picture and a benchmark table isn't.
8:53
Alex
Okay, so is there a real test in there?
8:57
Jordan
Further down, yes, and it's the useful part. Somebody pointed it at a real, messy project -- the kind with six moving pieces and years of duct tape -- and it lost to the expensive top-tier models. On simple, clean tasks it was great and cost almost nothing.
9:14
Alex
So the split is clean tasks versus real ones.
9:20
Jordan
And here's the line I keep seeing in the weeds. Around every model there's a wrapper -- the thing that decides which files to hand it, that retries when it fails, that checks the work before you see it. People call that the harness. And the smartest comment in the thread is: the harness is the product. Not the model name.
9:37
Alex
Which is inconvenient for everybody selling a model name.
9:42
Jordan
Extremely. Oh -- and Pro is the slow sibling. There's a Flash version that answers faster and handles far more people at once. So the flagship is the one you'd use least in a real product.
9:53
Alex
The flagship is the trophy.
9:56
Jordan
I wouldn't put this in front of a classroom, either. We get a version of this pitch weekly -- cheap model, big number, ship it to teachers. A tutor that's charming on a clean question and lost on a messy one is worse than no tutor, because a kid can't tell the difference.
10:11
Alex
That's the second-order thing you always land on and I always underweight.
10:16
Jordan
You weight the contract. I weight the twelve-year-old.
10:21
Alex
Qwen. Alibaba's model team. They posted a genuinely enormous model on Hugging Face -- that's the public site where anyone can put model files up for download. Two-point-four trillion parameters, which is about as big as these get. And for the first time they used the word open about their very top tier.
10:39
Jordan
So I can have it.
10:42
Alex
You can download it. That's not the same sentence.
10:46
Jordan
How big is the file?
10:48
Alex
People squeezed it down hard -- you can store all those numbers less precisely to save space -- and it still came out around one-point-three terabytes.
10:59
Jordan
That's not a laptop.
11:02
Alex
That's not a building most companies have. This is a datacenter thing. And there's a much smaller model that arrived a couple days later -- that one's the actual gift for normal people.
11:12
Jordan
Wait, that's a real point though. If the thing teachers or hobbyists can run is the small one, then the small one is the news and the giant one is--
11:21
Alex
The giant one is the press kit. Yes.
11:25
Alex
But here's what I actually opened. The license. It isn't one of the standard free ones. It's their own document with their own name on it.
11:34
Jordan
And what's in it?
11:36
Alex
Internal use is free. Use it inside your company, no problem. But if you turn around and sell access to it -- hosting it as a service -- or you build a coding assistant or an office productivity assistant with it, and your group makes more than fifty million dollars in any twelve months, you need a separate paid license from them.
11:54
Jordan
So the rule is aimed at exactly the two products that would compete with them.
12:00
Alex
Precisely those two. Sell the model, or build the assistant. Everything else, go ahead.
12:06
Jordan
That's not an accident.
12:08
Alex
It's a shape. Free to download, with the money doors closed. And there's a second clause -- if you get really big, a hundred million users a month or twenty million dollars a month, you have to show their model's name in your interface.
12:23
Jordan
So free distribution, mandatory logo.
12:27
Alex
A legitimate business -- just not generosity.
12:31
Jordan
Okay, I'll add the part I got stuck on. The scores printed on that download page are mostly from a different version -- the one they host and rent to you, which they call Max. Not the file you're downloading.
12:43
Alex
They're different products?
12:45
Jordan
Different enough. The rented one can look at images, has extra tools built in, and you can tell it to stop deliberating and just answer. The download is text-only and -- this one's odd -- you can't turn the deliberating off. It always thinks first.
12:59
Alex
So the scores on the page are for the thing you rent.
13:03
Jordan
And the scores came from different setups row to row anyway. Different wrappers. Which, going back to your DeepSeek line--
13:11
Alex
The harness. That was your line.
13:14
Jordan
I'm stealing it back.
13:18
Alex
The thread's other note is that Qwen's benchmark numbers and Qwen's real-world feel have not always matched. Which is a polite way of saying: check it yourself.
13:30
Jordan
Zed -- they make a code editor, the program developers write code in -- launched Delta. It's not a panel inside their editor, it's a separate app. The idea: you, other people, and AI agents all working in the same live coding session, and you can watch and review what the agents build.
13:48
Alex
Live like a shared document?
13:52
Jordan
Live like a shared document. The conversation and the actual code folder both sync in real time. Underneath it's still an ordinary git project -- git being the folder-history tool programmers already use every day -- so someone who never installs Delta doesn't notice anything. And it plugs into outside agents, starting with Claude Code, Anthropic's coding helper.
14:13
Alex
How available is it?
14:16
Jordan
Private beta. Invites just started. So nobody listening should picture this as a thing they can go get today.
14:23
Alex
Okay, noted. What's the thread doing?
14:27
Jordan
The loudest thing has nothing to do with the technology. It's people saying: I do not want an audience in my editor.
14:36
Alex
Coding as single player.
14:40
Jordan
A lot of that. It's the old argument about two people at one keyboard -- you lose your focus, but you share what you know. Which is the wrong fight to have about this product.
14:50
Alex
Why?
14:51
Jordan
Because there's a much better comment sitting further down with a fraction of the attention. Somebody said, roughly: I would rather have the Claude conversation that produced the mess than the final files.
15:03
Alex
Say more about that.
15:05
Jordan
When an agent writes code, the code is the least durable part. You'll delete half of it in a month. What you can never reconstruct is why -- what you asked for, what it tried, where you said no. And right now that lives in a chat window that closes.
15:20
Alex
And Delta is selling the recording.
15:24
Jordan
Delta is selling the recording. That's the product. The editor is the wrapper.
15:30
Alex
Huh. Okay, I came in thinking this was another surface that wants access to your code, and I still think that. But--
15:37
Alex
--you've moved me on what they're actually building. That's not multiplayer. That's a note that stays true. Right now you can leave a comment on one version of the code, the code changes underneath you, and the comment is pointing at nothing.
15:49
Jordan
Yes. That's it exactly.
15:52
Alex
I'll still name the incentive. "Multiplayer agents" is currently a phrase that raises money. There are several startups in that lane this year. Some of them are a keyword with an app attached.
16:06
Jordan
Fair. And the skeptic question for Zed is whether they needed a whole new app and a whole new syncing system, when git already does the history part.
16:15
Alex
Their answer is that git stores the files and they want to store the argument.
16:22
Jordan
Which brings me to why I actually care. At work, when a teacher and I make a lesson tool together, the good part is never the file. It's the twenty minutes where she says, no, not that, my kids will click the wrong thing. If I keep the file and lose that conversation, I've kept the receipt and thrown away the meal.
16:38
Alex
That's a better pitch than their blog post.
16:41
Jordan
They can have it. They're in private beta, they've got time.
16:45
Alex
Small thread, one clean punch. Anthropic has a help page saying: the things Claude writes for you from your inputs -- you own them.
16:54
Jordan
And the catch is in the terms.
16:57
Alex
The terms say you can't feed that text back into building a rival chatbot. Narrow stuff is fine -- sorting things into buckets, summarizing, pulling fields out of documents.
17:08
Jordan
So the ban is specifically on the one use that would make a cheaper Claude.
17:14
Alex
Their reason is partly safety -- they say the safety rules don't come along with the text -- and partly the obvious one. Don't use our machine to build our replacement.
17:25
Jordan
Ownership is a noun. The verb they care about is copying the teacher.
17:32
Alex
That's the whole story. You own it the way you own a rental car's interior.
17:37
Jordan
The thread's small -- under thirty points, a handful of comments -- and it's all the same shrug. They trained on everybody's writing without asking, and now the output has a chaperone.
17:48
Alex
And they'd say every lab does this, which is true, and doesn't help.
17:53
Alex
So: it's yours. Congratulations. Don't get ideas.
17:58
Alex
That's our audit for today. Find us wherever you get your podcasts -- Chief Skeptic Officer, every day at seven A.M. New York time.
18:05
Jordan
And tell us what you're skeptical about. We want the angle you can't stop chewing on.
18:11
Alex
Stay curious. Stay skeptical.
18:14
Jordan
Doubt both.
