BrokeIt - Trending Repos · All episodes: ↗

Grok 4.6 Scores 61, Warrant for LPRs, 16-Year SQLite Bug

2026-08-12 · 7 min

Listen · Apple Podcasts Listen · Spotify

Stories covered

Transcript

Intro

Sam: A score of 61. Which, in the world of AI benchmarks, is apparently a big deal.

Kai: I'm Kai.

Sam: And I'm Sam.

Kai: And this is Open Source After Dark for Wednesday, August 12th, 2026.

Sam: We've got a packed show for you today.

Kai: SpaceXAI's Grok is back with a new version, and it's supposedly climbing the leaderboards.

Sam: Next, we're digging into automated license plate readers, and whether police should need a warrant to track your car's every move.

Kai: And we'll wrap with a wild database mystery: Tailscale goes on the hunt for a bug that's been hiding in SQLite for sixteen years.

SpaceXAI's Grok 4.6 Scores 61 on the Artificial Analysis Intelligence Index

Kai: Alright, let's kick things off with Grok. SpaceXAI just dropped version 4.6.

Sam: Another Tuesday, another LLM.

Kai: [excited] No, but this one's interesting! The big number they're touting is a 61 on the Artificial Analysis Intelligence Index.

Sam: Sixty-one. Is that... good? I feel like these scores are just golf. Is a lower number better?

Kai: [laughs] Higher is better. It puts it right up there with top models from just a few months ago. The pace is just unreal.

Sam: Hold on. The 'Artificial Analysis Intelligence Index'. Is this a standard, respected benchmark, or one of those things a company spins up to make their own model look good?

Kai: It's a meta-benchmark! They pull from a bunch of different tests — MMLU, HumanEval, coding, math... the idea is to give a more complete picture of its abilities.

Sam: A holistic view that still puts it well behind the current top models from Anthropic and Google, right? The article says it's competitive, not leading.

Kai: Sure, but for an 'open-weights' model, it's a huge step. More competition is always a good thing.

Sam: I guess. But I get nervous when the hype cycle spins up around a single number on a proprietary index. What does a score of 61 feel like to use?

Kai: That's the next step, right? But the takeaway for developers is you're about to get another powerful, fine-tunable model that isn't controlled by the usual suspects.

Sam: [dry] And what it also means is, don't re-architect your entire AI strategy based on a press release. Wait for the real-world results.

License plate reader searches should require a warrant

Sam: Alright, let's pivot from AI hype to something much more grounded: surveillance. We're talking about automated license plate readers, or ALPRs.

Kai: Right, these are the cameras you see on police cars or light poles that just scan every plate that goes by.

Sam: Exactly. And private companies are building massive databases from this data and selling access to law enforcement. We're talking billions of location records on ordinary citizens.

Kai: Okay, but the argument has always been that you have no expectation of privacy on a public road. Your license plate is... public.

Sam: That's the old argument. This blog post makes a fantastic point: the scale changes the nature of the search. It's the difference between a cop remembering they saw your car, and a computer that can instantly pull up every place your car has been for the last five years.

Kai: Right, so it's basically mass, warrantless tracking.

Sam: Exactly. And the post argues this is a Fourth Amendment search that should require a warrant. Otherwise, police can just go on a fishing expedition through your entire life's travel history.

Kai: Wow. And you could see where that would have a chilling effect on things like attending a protest or a political rally.

Sam: Or visiting a doctor, a therapist, a lawyer... you name it. The bottom line is that without clear legal guardrails, a huge part of your physical life is being logged and made searchable by the government, often without any suspicion of wrongdoing.

Kai: That's a really good point. The convenience for law enforcement can't just bulldoze fundamental privacy rights.

Tailscale Traces Database Corruption to 16y/o SQLite WAL-Reset Bug

Kai: Alright, let's wrap with a classic detective story. Tailscale published an incredible deep-dive on a database corruption bug they were hunting down.

Sam: Oh, I love a good bug hunt story.

Kai: So they were seeing this super rare data corruption in their coordination server... and they tracked the cause all the way back to SQLite.

Sam: Wait, SQLite? The most deployed, most tested database engine in the world? The one that's literally on your phone right now?

Kai: The very same. And get this... the bug is sixteen years old.

Sam: Sixteen?! No way. What was it?

Kai: It's a really specific edge case. It only happens if you're using Write-Ahead Logging—WAL mode—and you issue a certain PRAGMA command on an empty database. It could fail to reset the WAL state, creating a nasty race condition.

Sam: That is... obscure. I'm impressed they even found it.

Kai: The write-up is just a masterclass in debugging. They built custom tools, bisected the entire SQLite source history... the whole thing is incredible.

Sam: But it's also terrifying. A sixteen-year-old bug in a foundational piece of software that everyone, including us, relies on. That's a supply chain nightmare.

Kai: I see it as the opposite! It's proof the system works. The bug was found, a patch was submitted upstream by Tailscale, and now SQLite is even more robust.

Sam: So what's the takeaway for the rest of us?

Kai: It means read the Tailscale blog post, it's fantastic. And maybe have a little appreciation for the giants whose shoulders we stand on.

Sam: And it means update your dependencies. And remember that even the most 'stable' software has dragons hiding in sixteen-year-old code.

Kai: Alright, quick recap: SpaceXAI is still pushing the performance of its Grok model.

Sam: And a growing movement is calling for warrants before police can search those massive license plate databases.

Kai: And a fantastic bit of detective work from Tailscale unearths a 16-year-old bug in SQLite.

Kai: And before we go, a quick PSA. Today, August 12th, is World Elephant Day.

Sam: [dry] Are we getting an open-source project for pachyderm portfolio planning?

Kai: [laughs] No, but it's a good excuse to remind everyone that if you're looking for a federated, open-source social network... there's always Mastodon.

Kai: And that's our show for Wednesday, August 12th, 2026. Thanks for listening.

Sam: We'll be back tomorrow. Until then, maybe go double-check your database journaling modes.

This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.