Sovereignty

Why This Matters: The Night They Flipped the Switch On June 12, 2026, a frontier AI model that millions of people were using vanished for the entire planet overnight — not because it broke, but because a government letter ordered it pulled over a bug the vendor itself called minor. One day after launch. Gone, for everyone. I watched it happen in real time, mid-project. The full story — and why it’s the 1990s Crypto Wars all over again — is in The Crypto Wars, Round Two. The takeaway that matters here is simpler: if your tools live on someone else’s servers, your access is a permission, not a possession — and permissions get revoked. ...

The Problem: Amplified Hallucination Guide #1 in this series showed you how to run a local coding agent on your own hardware. Revocation-proof, zero per-query cost, no export-control letter touches it. What it did not cover — because it revealed itself mid-session — is the follow-on problem: the model will lie to you about whether what it built works. Not the obvious kind of lie. Not “I am unable to complete this task.” The dangerous kind: a polished, correctly-shaped, plausibly-commented artifact that is quietly broken, delivered with a confident task-complete. ...

Episode 15: Why Linux? Your browser does not support the audio element. Download MP3 Duration: ~12 minutes | Format: Practical Episode Summary You can install all the privacy tools you want, but if your operating system is hostile, you’re building on a compromised foundation. This episode makes the case for owning your computing stack with Linux. This episode reveals: The Windows problem: Telemetry you can’t turn off, Cortana, advertising IDs, forced updates, OneDrive Why Linux is different: Open source, no business model that needs your data, choice and control, respect by default The intimidation myth: Why “Linux is too hard” hasn’t been true for over a decade Choosing a distro: Mint, Pop!_OS, Ubuntu, Fedora for beginners; Debian and Arch for the curious A gentle migration: Live USB, dual-boot, a designated machine, then full Linux What you gain: Ownership, longevity, understanding, community, privacy by design Key Quotes “You can install all the privacy tools you want. But if your operating system is hostile, you’re building on a compromised foundation.” ...

AI is a tool — same as a knife. It cuts bread or it cuts a person; the blade doesn’t decide. The user does. Right now, most of the AI you see is pointed at control. Surveillance sold as convenience, feeds tuned to keep you scrolling, systems built to sort and score people. So if your honest read is “this thing is mostly used for bad” — you’re not wrong about what’s in front of you. ...

I found out the way you find out about most things that matter: by accident, in the middle of doing something else. A while back I’d built a small AI voice red-teaming lab — a setup to stress-test how well AI voice assistants hold up against manipulation — and I’d gone back in to revisit the project. A few prompts deep, the model threw up a bright-yellow banner: it had flagged something in my session for safety and was bumping me down to an older model, mid-task. Mildly annoying, but fine — these things have tripwires, and I figured I’d brushed one (I was using words like “exploit” and “red-team” while documenting a defensive tool; classifiers get jumpy). ...

Starting in September 2026, Google will require every Android app developer to register with Google, submit government-issued identification, and pay a fee before their apps can be installed on any certified Android device. This includes apps you sideload. Apps from F-Droid. Apps from Aurora Store. Apps you build yourself. If the developer hasn’t registered with Google, the app won’t install. What Google Is Actually Doing Google announced this policy in August 2025 under the banner of “developer verification.” Here’s what it requires: ...