IndexDB isn't cutting it anymore. We've been working on a new client-side database written in Rust using OPFS for our next sync engine in @linear.
It indexes everything. As a drop-in, API-compatible replacement it's faster than IndexDB (which is surprising!), but it absolutely DESTROYS it when you do complex, multi-key queries. And while IndexDB queries slow down linearly as row count increases, our new database stays almost flat. It's like 600x faster with usage we see in Linear, more if you got to large workspaces.
We do want to open-source it, but we can't before we decide on the name. We've got two strong candidates:
- postindex
- sub-linear
Which one do you like more?
remember that wave of ai psychosis from the beginning of the year?
what lasting software came out of that? the entire discussion was everyone marveling at the process
you gotta learn the lesson that techniques aren't worth discussing until you see impressive output
man, who should i trust? a bunch of nerds who made linux run on apple silicon, reverse engineering that pesky gpu isa among a gazillion other things, all pre-ai.
or the guy who thinks having your agent rewrite shitty rust he never looked at in x86_64 is excellence?
I can't shake the conviction software is not dead. At least for some types of software and until we move far beyond LLMs to models with no training-inference distinction and no reliance on human language. h/t @AndrasGerlitsrichiejp.com/the-last-softwa…
we gave a fortune cookie your timeline
and it did its homework 🥠
→ type your handle
→ it reads your posts
→ it tells your future
it’s a little too accurate 👇
thine.com/x/fortune/SAtIwq1s…
For the second time in Google Chrome’s history, Google awarded a $250,000 bounty for a full-chain exploit… to @XBOW. Here’s the full story:
At an all-hands at the start of 2026 in Malta, I set the team a crazy challenge. A full-chain exploit of Chrome by the annual Black Hat cybersecurity conference in August.
I believed there were few better tests of whether @XBOW could move beyond web applications to desktop software, servers and devices.
Chrome is one of the most hardened pieces of software on the planet, used by more than half the world’s population.
A full-chain exploit lets an attacker take total control of a machine, where they can read every email, password and bank login the user types. You don’t need to download anything or click a phishing link. Visiting the wrong site is enough.
So @moyix, Andres Luksenberg, Baul Lee, and Willem Pinckaers took on the challenge along with a fifth teammate: OpenAI's GPT-5.6 Sol.
They built a chain they thought would win, but Google told us they already knew one of the bugs.
We were already in Las Vegas for Black Hat and DEF CON, and the team didn’t want to go home without the win.
So Brendan and the agents built a new exploit in just 6 days.
We submitted it to Google and waited.
The news came through that we'd done what should’ve been impossible. A full-chain bounty of $250,000, the first awarded under Google’s 2026 rules.
It took just 6 days and $40,000 of compute to construct an exploit that affects a billion users of Chrome on Windows. An intelligence-agency veteran told me his team used to spend 6 months on this kind of vulnerability.
My takeaway: the cost of finding truly critical vulnerabilities is collapsing, for attackers and defenders alike. Restricting powerful models is not the answer; GPT-5.6 Sol is already public.
But defenders have one advantage attackers never will: they can test their own code first.
Assume your software is exploitable. Whoever is hunting your bugs has the same building blocks we did.
This is cause for urgency but not panic.
XBOW is now developing an autonomous product for testing compiled software (desktop applications, servers, embedded devices), and partnering with the world’s top organizations to design that product.
If you’d like to be one of them, get in touch.
P.S. Restart Chrome whenever the Update button appears!
Introducing ThyVoice: our state-of-the-art approach to solve "who said what" across conversations at 10x lower cost.
We benchmarked 8 speech systems, built on OpenAI, ElevenLabs, Deepgram, AssemblyAI, pyannoteAI and the academic baselines. ThyVoice made the fewest errors.
@ThineAI is a slow burn...
It’s not a "recorder". Not a “personal agent”. Not a memory app.
It’s something else entirely.
Something you couldn’t imagine before experiencing it