<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sovereignty on Tom Meurs</title>
    <link>https://tommeurs.nl/en/tags/sovereignty/</link>
    <description>Recent content in Sovereignty on Tom Meurs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© Tom Meurs</copyright>
    <lastBuildDate>Tue, 06 Oct 2026 09:00:00 +0200</lastBuildDate>
    <atom:link href="https://tommeurs.nl/en/tags/sovereignty/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Talos Linux Vendor Lock-In: Five Questions, Run on My Own Nodes</title>
      <link>https://tommeurs.nl/en/posts/talos-linux-vendor-lock-in/</link>
      <pubDate>Tue, 06 Oct 2026 09:00:00 +0200</pubDate>
      <guid>https://tommeurs.nl/en/posts/talos-linux-vendor-lock-in/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; I ran the five questions from my licence post on the OS under my own cluster. The licence holds. The &lt;span class=&#34;def&#34; tabindex=&#34;0&#34; data-def=&#34;A Linux distribution with no shell, no SSH and no package manager, managed entirely through an API. The node is configuration rather than a machine you log into.&#34;&gt;Talos&lt;/span&gt;&#xA; Linux vendor lock-in sits in two defaults that point at Sidero&amp;rsquo;s servers, the &lt;span class=&#34;def&#34; tabindex=&#34;0&#34; data-def=&#34;Business Source License 1.1: the source is published and free to use, except for the use the licensor names, usually a hosted service that competes with its own. Each release converts to an open source licence after a fixed number of years.&#34;&gt;BSL&lt;/span&gt;&#xA; code Sidero keeps adding around the &lt;span class=&#34;def&#34; tabindex=&#34;0&#34; data-def=&#34;Mozilla Public License 2.0: a file-level copyleft licence. Changes to MPL files must stay open when you distribute them, while code in other files may carry any licence.&#34;&gt;MPL&lt;/span&gt;&#xA; core, and a company Yardi has owned since 14 September.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Your Dependency&#39;s Business Model Is Part of Your Threat Model</title>
      <link>https://tommeurs.nl/en/posts/license-change-supply-chain-risk/</link>
      <pubDate>Wed, 23 Sep 2026 19:00:00 +0200</pubDate>
      <guid>https://tommeurs.nl/en/posts/license-change-supply-chain-risk/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; A vendor freezing its free edition belongs in your risk register next to the expiring certificate. Thirty-six dated cases below, three kinds of event, and five questions to score your own stack. My own register had the Vault row missing for three years.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;On 11 September, Portainer&amp;rsquo;s CEO published &lt;a href=&#34;https://www.portainer.io/blog/portainer-3-0-is-coming&#34;&gt;&amp;ldquo;Portainer 3.0 is coming, and here&amp;rsquo;s what it means for you&amp;rdquo;&lt;/a&gt;. I read it the Monday after and shrugged.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s what it says. 3.0 is a Kubernetes-first codebase for enterprise customers, and &amp;ldquo;we are not cutting a separate CE build of it&amp;rdquo;. Community Edition stays on 2.x. 2.45 LTS &amp;ldquo;is the last release in the 2.x line&amp;rdquo;. A few days later they added a clarification: 2.45 keeps getting security fixes, bug fixes and back-ports of any 3.x feature that has a Docker API equivalent, &amp;ldquo;for as long as that LTS is supported&amp;rdquo;. The &lt;a href=&#34;https://docs.portainer.io/start/lifecycle&#34;&gt;lifecycle page&lt;/a&gt; puts that at May 2027. Want 3.x for free? There&amp;rsquo;s a Business Edition key called &lt;a href=&#34;https://www.portainer.io/take-3&#34;&gt;3 Nodes Free&lt;/a&gt;, one per organisation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Linux Is for Everyone: Why This Blog Now Welcomes Beginners Too</title>
      <link>https://tommeurs.nl/en/posts/linux-is-for-everyone/</link>
      <pubDate>Thu, 11 Jun 2026 20:28:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/linux-is-for-everyone/</guid>
      <description>&lt;p&gt;My neighbour is 70 years old. He&amp;rsquo;s used Windows his whole life. Last month he asked me: &amp;ldquo;Tom, I keep hearing about Linux. Is that something for me too?&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;He&amp;rsquo;s not the first. Over the past year I&amp;rsquo;ve had the same question from friends, family and colleagues, each in their own shape. &amp;ldquo;I want to get off Windows, but where do I start?&amp;rdquo; &amp;ldquo;Is Linux hard?&amp;rdquo; &amp;ldquo;Can I still use my normal programs?&amp;rdquo; To me these are easy questions. I&amp;rsquo;ve been running Linux since SuSE 6.0, back when you picked your hardware by whether a Linux driver existed for it. If you&amp;rsquo;ve never seen a terminal, they&amp;rsquo;re not easy at all.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Data Poisoning: Reclaiming Your Privacy Through Offence</title>
      <link>https://tommeurs.nl/en/posts/data-poisoning-privacy/</link>
      <pubDate>Sun, 07 Jun 2026 21:43:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/data-poisoning-privacy/</guid>
      <description>&lt;p&gt;Here&amp;rsquo;s how privacy works today. You read the policy. You dismiss the cookie banner. You hunt through three settings menus for the opt-out toggle that someone buried on purpose. All of that to exercise a right that should&amp;rsquo;ve been the default. And while you&amp;rsquo;re still on the first paragraph of the terms of service, every click, scroll, hover and the exact timing of your keystrokes has already been harvested, packaged and sold. Somewhere along the way I stopped finding that strange, and that bothers me more than the harvesting does.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Quantum-safe GPG identity with multiple aliases</title>
      <link>https://tommeurs.nl/en/posts/quantum-safe-gpg-identity/</link>
      <pubDate>Sat, 18 Apr 2026 10:47:00 +0200</pubDate>
      <guid>https://tommeurs.nl/en/posts/quantum-safe-gpg-identity/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; One GPG masterkey that only certifies, kept offline. Three aliases bound to it, so anyone can check they&amp;rsquo;re the same person. Ed25519 subkeys for signing and SSH, an ML-KEM plus X448 subkey for encryption so recorded ciphertext stays closed after a quantum computer shows up, and three backups that each assume the other two are gone. Needs GnuPG 2.5.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;A cryptographic signature still means exactly what it says. If the key is yours and the signature verifies, the content came from you. No vendor handed you that identity, no CA can pull it, no platform can suspend it. It exists because you generated the key, and it&amp;rsquo;s yours for as long as you hold the private half. Most of what gets called &amp;ldquo;online identity&amp;rdquo; is borrowed. A handle someone can ban, an email address the domain owner can take back the day they feel like it. A GPG signature sits outside all of that.&lt;/p&gt;</description>
    </item>
    <item>
      <title>K8sGPT with a Local 70B Model on Apple Silicon</title>
      <link>https://tommeurs.nl/en/posts/k8sgpt-local-llm-cluster-management/</link>
      <pubDate>Thu, 05 Feb 2026 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/k8sgpt-local-llm-cluster-management/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; I pointed K8sGPT at a Llama 3.3 70B model running on a Mac Studio in my own office, so no cluster metadata leaves the network, and fed it three broken workloads. It found all three and wrote fixes I&amp;rsquo;d accept from a colleague, except for the resource numbers, which it made up. Assisted diagnosis works, at 25 seconds a query. Autonomous cluster management is still marketing, and the security section is why I wouldn&amp;rsquo;t let a model change anything on its own.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why Privacy Matters More Than Ever</title>
      <link>https://tommeurs.nl/en/posts/why-privacy-matters-now/</link>
      <pubDate>Mon, 02 Feb 2026 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/why-privacy-matters-now/</guid>
      <description>&lt;p&gt;Your phone logged where you slept before you woke up. You check Gmail, search something on Google, message a friend on WhatsApp, pay for coffee with a card and walk past a dozen cameras before lunch. None of that feels like surveillance. It feels like a normal morning.&lt;/p&gt;&#xA;&lt;p&gt;It felt the same five years ago, and I want to show you what changed in between. The comfortable version of privacy, &amp;ldquo;I have nothing to hide&amp;rdquo;, has quietly stopped being true, and I think most people haven&amp;rsquo;t noticed. Three things happened at once. On its own each one is manageable. Together they&amp;rsquo;re what worries me.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Hardware Ownership Paradox: When Sovereignty Gets Expensive</title>
      <link>https://tommeurs.nl/en/posts/hardware-ownership-paradox/</link>
      <pubDate>Fri, 30 Jan 2026 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/hardware-ownership-paradox/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;https://tommeurs.nl/en/posts/self-hosting-for-everyone/&#34;&gt;previous post about self-hosting for everyone&lt;/a&gt; I drew a hopeful picture of managed self-hosting, where anyone can own their data. I skipped over something, and it&amp;rsquo;s been bugging me since. Hardware costs money, and the sum comes out very differently depending on whether a business or a person is paying.&lt;/p&gt;&#xA;&lt;p&gt;So here are two rules. Both sound reasonable on their own. Then I&amp;rsquo;ll put them in the same room.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosting for Everyone: A Vision for Digital Agency</title>
      <link>https://tommeurs.nl/en/posts/self-hosting-for-everyone/</link>
      <pubDate>Tue, 27 Jan 2026 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/self-hosting-for-everyone/</guid>
      <description>&lt;p&gt;Most people keep their photos at Google, their mail at Gmail, their documents in whatever cloud came with the phone and their passwords in a browser built by an advertising company. Every byte sits on a server they don&amp;rsquo;t own, under terms they didn&amp;rsquo;t read, in a country they didn&amp;rsquo;t check. Nobody finds that strange anymore, because the alternative looks like a second job.&lt;/p&gt;&#xA;&lt;p&gt;I want to talk about that alternative, and about why it sits behind a wall most people will never climb.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vault for Beginners: Secrets Management in Kubernetes</title>
      <link>https://tommeurs.nl/en/posts/vault-beginners-kubernetes/</link>
      <pubDate>Wed, 02 Jul 2025 10:00:00 +0200</pubDate>
      <guid>https://tommeurs.nl/en/posts/vault-beginners-kubernetes/</guid>
      <description>&lt;p&gt;The first time I ran &lt;code&gt;kubectl get secret myapp -o yaml&lt;/code&gt; and base64-decoded the value, I felt my stomach drop. There was my database password, sitting in etcd, readable by anyone who could reach the API with the right RBAC. Kubernetes Secrets are not secrets. They&amp;rsquo;re base64-encoded plain text with a fancy name. That&amp;rsquo;s the default, and it&amp;rsquo;s the thing nobody warns you about on day one.&lt;/p&gt;&#xA;&lt;p&gt;Every cloud provider has a fix for sale. AWS has Secrets Manager, Google has Secret Manager, Azure has Key Vault. They work. The catch shows up later: the day you need to migrate, the day you want to know exactly what happens to a secret after you write it, the day you realise your most sensitive data lives in a system you can&amp;rsquo;t inspect.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Running Kubernetes Offline: Edge Computing Without Internet</title>
      <link>https://tommeurs.nl/en/posts/kubernetes-offline-edge/</link>
      <pubDate>Tue, 04 Mar 2025 20:47:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/kubernetes-offline-edge/</guid>
      <description>&lt;p&gt;What happens when your Kubernetes cluster can&amp;rsquo;t reach the internet? I don&amp;rsquo;t mean a slow connection. I mean no connection at all. Ships at sea. Remote mining sites. Factory floors with air-gapped networks. Military deployments.&lt;/p&gt;&#xA;&lt;p&gt;For a lot of people that sounds exotic, like a problem someone else has. I treat it as a baseline design requirement, and I&amp;rsquo;ll explain why it makes my homelab better even though I almost never actually pull the cable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
