From the Rubble | Digital Sovereignty Series | Episode 1

TLDR: Windows 11 phones home constantly, ships ads in the Start menu, forces AI you didn’t ask for, and is engineered to push functional hardware toward obsolescence to sell new machines. A programmer who was running Debian before Ubuntu existed stayed on Windows too long out of habit - here’s what finally broke that inertia, how Aurora Linux was chosen for three laptops, why the one with discrete NVIDIA graphics needed Bazzite instead, and what immutable Linux actually means for daily use.

Let’s start with what you’re actually running.

Windows 11 phones home constantly. Not occasionally. Not when you update. Constantly. Telemetry, diagnostic data, app usage, typing patterns, location, browsing behavior - all of it flowing back to Microsoft servers by default. You can turn some of it off. You can’t turn all of it off. The operating system you paid for, running on hardware you own, is reporting on you around the clock.

That’s not paranoia. That’s documented behavior in Microsoft’s own privacy statement, buried in language designed to be ignored.

I say this as someone who knew better for a long time and stayed anyway.

1. The Part Where I Admit I Had No Excuse

I was writing code professionally for ten years. I was running Debian before Ubuntu existed - back when Linux desktop meant fighting dependency hell and hand-editing config files at 2am. I knew the ecosystem. I knew what it could do. I watched it mature into something genuinely usable while I stayed on Windows out of habit and inertia.

That’s the honest version. Not “Linux wasn’t ready.” Linux was ready. I just hadn’t reached my threshold yet.

The threshold arrived on multiple fronts at roughly the same time.

2. The Microsoft Indictment

Windows 10 end of life. Microsoft pulled support for Windows 10 in October 2025 — that date has now passed. Their answer was Windows 11 - which conveniently requires a TPM 2.0 chip and specific CPU generations that a massive percentage of existing, fully functional hardware doesn’t meet. This isn’t a technical necessity. It’s a forced obsolescence play. Millions of machines that run perfectly well, pushed toward landfill to sell new hardware and migrate users to a platform with more aggressive data collection architecture.

The AI that wasn’t asked for. Copilot is not a productivity feature. It’s a data product with a chat interface - trained on your usage, connected to your files, running in the background of an OS you already paid for. Microsoft has been told this, clearly and repeatedly, by users and enterprise customers. The response has been to embed it deeper with every update. That’s not a company responding to feedback. That’s a company that has decided your preferences are noise.

AI should be a choice. A tool you opt into, understand, and control. What Microsoft shipped is the opposite: an always-on behavioral observation layer dressed up as an assistant. When I want AI in my workflow - and I do use it deliberately - I want to be the one who chose it, configured it, and understands what it’s doing. Episode 4 covers exactly that. This is not that.

The retail signal. HP has been shipping Linux machines for a while. Lenovo recently followed. Major hardware manufacturers don’t bet shelf space on products that don’t have a market. When the laptop you can buy at a mainstream retailer ships with PopOS instead of Windows, the “Linux is for nerds” argument is functionally dead. The mainstream is arriving whether Microsoft likes it or not.

And then there’s Bill Gates. I’ll keep this brief because it deserves more space than a paragraph and more research than I’ll ask you to take my word for. The Epstein connections are documented. The behavior patterns that emerged over the last several years are documented. The philanthropic empire built on top of Microsoft’s monopoly-era practices has its own set of uncomfortable questions about who benefits and how. I’m not telling you what to conclude. I’m telling you I looked at the founder and the company he built and stopped being surprised that the product treats users the way it does. Organizations reflect their founders. Worth drawing your own line.

3. What’s Actually Happening When Windows Runs

Here’s the practical picture of what Microsoft’s telemetry collects by default: application usage and frequency, websites visited through Edge, search queries, device location, voice input when Cortana or Copilot is active, diagnostic error data that includes file paths and recently used documents, and hardware performance metrics tied to your Microsoft account.

Some of this you can disable in settings. Microsoft has made the full disable path deliberately non-obvious, split across multiple menus, and in some cases re-enabled after updates. The reasonable interpretation of that pattern is that the data has value to them and they’d prefer you not turn it off.

The operating system as surveillance infrastructure isn’t a new idea - it’s been the direction of travel since Windows 10. Windows 11 is a further iteration of the same trend, not a departure from it.

When I put it that way, the question isn’t “why would you switch to Linux?” The question is “why would you stay?”

4. The Sovereignty Question

Here’s the frame I use for every tool decision: do I own this, or does it own me?

Same question I ask about health systems, financial systems, food systems. Who controls the thing? What are their incentives? What happens when those incentives stop aligning with mine?

With Windows, the answers are: Microsoft owns it. Their incentive is to monetize your attention and data indefinitely. And when those incentives diverge from yours - which they already have - you have no recourse. You agreed to the terms. You’re the product.

Linux is a different answer to that question. Open source. Auditable. Free. Maintained by a global community with no unified commercial agenda. No one is building a behavioral profile from your usage. No one is pushing an unwanted AI assistant because a product team needs to justify a roadmap item.

You own the tool. The tool does not own you.

That’s not a technical argument. That’s a values argument. And it’s the one that finally made the decision obvious.

series: [“Digital Sovereignty”]

5. Immutable Linux - Why This Flavor Matters

Not all Linux is the same, and I want to be specific about what I chose and why, because it matters for how the rest of this series works.

Traditional Linux distributions are mutable - you install packages, make system changes, and over time the system drifts from its original state in ways that accumulate technical debt. This is how Linux has worked for decades and it’s fine, but it’s also why “I broke my Linux install” is a thing people say.

Immutable Linux distributions flip this architecture. The base operating system is read-only. It doesn’t change between updates. When an update arrives, you’re not patching a running system - you’re deploying a pre-tested image and rebooting into it. If the new image has a problem, you boot the previous one from the menu. Rollback in under a minute.

Your applications live in containers - primarily Flatpaks - cleanly separated from the base system. The OS stays clean. The apps stay isolated. The whole thing is more resilient by design.

For someone who thinks in systems, this architecture is immediately legible. Immutable base, containerized applications, atomic updates, defined rollback paths. It’s how you’d design a resilient system from scratch.

Two distributions stood out in my research: Aurora and Bazzite. Both are built on Universal Blue, which sits on top of Fedora. Both are immutable. Both are actively maintained with real communities. The distinction is primary use case - Aurora is built for general desktop productivity and development, Bazzite is built with gaming and NVIDIA hardware as first-class concerns.

6. Three Laptops, One Problem

I did a proper needs assessment before touching anything. Values first, then workflow requirements, then hardware inventory. Landed on Aurora - made sense on paper for a productivity-primary user.

Installed it on three laptops.

Two of them worked exactly as expected. Clean installs, everything functional, genuinely impressive out-of-the-box experience. The Aurora team has done serious work.

The third laptop has discrete NVIDIA graphics alongside integrated Intel - an Optimus configuration. On Windows this switching happens automatically. On Linux it has historically been one of the rougher edges, and Aurora isn’t specifically built to smooth it.

I worked through EnvyControl, the standard tool for managing Optimus switching. Tried every configuration - integrated only, discrete only, hybrid. The performance issues in gaming scenarios didn’t resolve the way they should have. I spent real time on this. It wasn’t a quick try-and-give-up situation.

Eventually I made the call: clean install of Bazzite on the NVIDIA machine. Bazzite handles NVIDIA Optimus as a primary use case. The switching that required manual configuration and still wasn’t right on Aurora worked correctly on first boot under Bazzite.

Sometimes the right move is acknowledging you made the wrong call first and correcting it cleanly. The wrong call here wasn’t careless - Aurora was the right choice based on my assessment. The NVIDIA Optimus edge case only surfaced on one machine of three, and it had a clean solution.

7. The Rebase vs. Clean Install Decision

Worth a brief mention for anyone who goes down this path: immutable Linux distributions built on Universal Blue support rebasing - switching from one image to another without a clean install. It’s one of the genuinely elegant things about this architecture. You could go from Aurora to Bazzite without reinstalling, keeping your home directory and applications intact.

I chose a clean install anyway. I’d accumulated enough configuration on that machine that starting from a clean baseline made more sense than carrying state across. It also let me document the setup process properly, which serves this series.

If you’re in a situation where a clean install isn’t practical, rebasing is a legitimate path. For a fresh start, I’d go clean.

8. What Immutable Means Day to Day

If you’re new to this, the practical reality:

Updates are atomic. Apply, reboot, done. New image staged before the reboot. Previous image available if something goes wrong. No “configuring updates 34%” at midnight.

Applications come from Flatpak. The ecosystem is extensive and covers the vast majority of what you’d need. For edge cases, Distrobox lets you run traditional Linux containers alongside the immutable base without touching it.

The base doesn’t drift. Six months from now, the core OS will be functionally identical to install day, just on a newer image version. No accumulated cruft, no mystery performance degradation.

You don’t need to be a power user. Both Aurora and Bazzite are built for people who want a modern desktop without managing a server. The terminal is available when you need it. Daily use doesn’t require it.

series: [“Digital Sovereignty”]

9. The Two Laptops That Just Worked

Worth being explicit: two of three machines had completely uneventful Aurora installs. They’re daily drivers now. No ongoing issues.

For machines without discrete NVIDIA GPUs or without Optimus configurations, Aurora is a strong choice. The NVIDIA Optimus edge case is specific hardware - not a reason to avoid Aurora broadly. If you’re unsure about your hardware, protondb.com and the Aurora community forums are good research starting points.

10. Where This Leaves You

Three laptops. Two on Aurora. One on Bazzite. All three off Windows.

The transition took more time than reinstalling Windows would have. Real time went into the NVIDIA machine. None of it was catastrophic. All of it was solvable. And the programmer in me - the one who was running Debian before Ubuntu existed - knew it would be, which probably made it easier to stay with it through the friction.

On the other side: three machines that don’t report to Microsoft. No ads in the Start menu. No Copilot that can’t be removed. No forced update path designed around someone else’s hardware sales cycle. No operating system whose founder’s public behavior I have to compartmentalize to use it.

The friction was temporary. The freedom is permanent.

11. Resources

Next episode: You’ve got a fresh Linux install. Now lock it down. First boot hardening, firewall, DNS privacy, and what’s actually listening on your network - including the thing you didn’t expect.

From the Rubble is written by Kala - veteran, 30-year conspiracy realist. Digital sovereignty, health sovereignty, and the overlap between them. No corporate funding. No ads. No permission required.

Tool: Replaces: Why It Made the Cut: