← Feed

Posts

• Finally done with the distro-hop: My return to Fedora

  Two years into full-time Linux and I’m finally burning the distro-hopping cycle. I fell for the Arch/AUR trap for a while, but I got tired of spending my weekends debugging file manager crashes instead of maintaining my home lab. Switched back to Fedora, and it’s boring in exactly the way I need it to be. It’s a stable launchpad for my projects, not the project itself.

• Why I moved my Plex library to Jellyfin after 14 years

• [Tool] Privacy-focused AUR Malware Audit Tool (Atomic Arch Incident)

  The “Atomic Arch” campaign compromised over 1,500 AUR packages between June 10-12, targeting SSH keys and API tokens. If you updated via yay or paru during that window, you need to audit your local system. I’ve built a client-side tool to help with this. Local Processing: Your package list never leaves your browser. All comparisons are done client-side. Live Data: It fetches the verified malicious list directly from the official Arch servers (md.archlinux.org) to ensure it’s always current...

• Replacing Tailscale with a 2-VPS WireGuard setup (No port forwarding)

  I wanted to move away from Tailscale but found Headscale a bit too convoluted for what I actually needed. Ended up with a simple WireGuard setup using two VPSes: one as a VPN hub, the other acting as a reverse proxy back into my home lab. It lets me expose services publicly without any inbound port forwarding on my home connection.

• Turns out I have been updating wrong all this time! 🤦🏼

  I’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done. Turns out I was wrong. I was checking CVE‑2026‑31431 (Copy Fail) this morning and realised that despite my “successful” updates, I was still running a vulnerable kernel from March. I’ve had to rethink how I handle host updates. If you’re relying on a standard upgrade and a reboot to keep Proxmox or Debian hosts safe, you might want to check if yours...

• Reclaiming the desktop: Why I’m still on Linux in 2026

  I’ve been using Linux for years, but as the proprietary alternatives get more aggressive with telemetry and adverts, I wanted to document the choices that actually keep my desktop predictable. This isn’t a manual, but a practical overview of my setup. From why I’ve settled on CachyOS and KDE Plasma for my main rig, to the reality of dealing with proprietary software and app compatibility in 2026. It’s just an honest look at the transition and why I’m done with the corporate defaults.

• Why I’m skipping the proprietary "Little Snitch" for Linux

  I saw the news about Little Snitch coming to Linux via eBPF and Rust. On paper, it looks fancy. In reality, the backend is closed source. Personally, I don’t see the point in installing a proprietary black box to monitor other black boxes. I’m sticking with my AdGuard Home setup and OpenSnitch for when I actually need to trace a binary. I wrote up my thoughts on why I think this is a solved problem for most FOSS-first home labs.

• Post #972539

  It’s less about a “scan” and more about the “handshake.” Look at things like Windows 11 requiring a TPM and Secure Boot, or the Microsoft Pluton chip being baked into newer CPUs. They don’t need to inspect your code. They just need a cryptographic “attestation” that says your hardware and kernel are in a “known good” state. If your DIY kernel doesn’t have the right digital signature from the manufacturer, the service whether it’s a bank or a Netflix stream, simply says “computer says no” and d...

• Post #972206

  It is a myth, always has been. But the worry isn’t the “Year of Linux” happening, it’s the corporate version of it being forced on us via regulation.

• Is the "Year of Linux" actually a trap?

  I’ve spent years championing Linux as the only escape from Big Tech, but I’m starting to get twitchy. While we’re distracted by the Steam Deck making Linux “mainstream,” the corporate players and politicians are busy building a digital cage. Between California’s AB-1043 mandates and Microsoft’s “Face Check” infrastructure, I’m worried we’re heading for a hard schism: “Sanitised Linux” vs the “Free Rebel” distros. If the compliant, age-gated version becomes the industry standard, where does t...

• BrowserGate: Technical breakdown of LinkedIn’s covert browser extension fingerprinting

  LinkedIn is using hidden JS to scan your browser for over 6,000 specific extension IDs via a known Chromium vulnerability. By inventorying your local software, they can infer highly sensitive “Special Category” data like health status, religion, and political advocacy without consent. I’ve joined the dots on why Chromium-based “Shields” fail here and how to harden your home lab/network to stop the leak.

• Google’s Sideloading Crackdown: Why It’s a Threat to Everyone’s Privacy and Freedom

  Google is tightening control over Android under the guise of ‘security,’ but this crackdown on sideloading is a direct hit to digital sovereignty and FOSS. I’ve written about why this matters for our privacy and the future of open platforms. What do you think—is this the end of Android’s ‘open’ era?