<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FOSS – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/foss/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Sun, 14 Dec 2025 20:00:00 +0100</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/foss/index.xml" rel="self" type="application/rss+xml"/><item><title>On Digital Sovereignty, De-Americanizing My Software Stack, and Running WhatsApp in a Sandbox</title><link>https://www.apt-upgrade.me/2025/12/14/on-digital-sovereignty-de-americanizing-my-software-stack-and-running-whatsapp-in-a-sandbox/</link><pubDate>Sun, 14 Dec 2025 20:00:00 +0100</pubDate><guid>https://www.apt-upgrade.me/2025/12/14/on-digital-sovereignty-de-americanizing-my-software-stack-and-running-whatsapp-in-a-sandbox/</guid><description>&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; For years I have been toying with the idea of gradually freeing myself from US-centric software – not out of ideological purity, but to minimise unnecessary data exposure. It has turned into a personal experiment. One building block: WhatsApp and other apps I cannot do without run isolated in a sandbox on my phone.&lt;/p&gt;&#10;&lt;article class="post-content"&gt;&#10;&lt;section&gt;&lt;h2&gt;Why This Experiment Exists&lt;/h2&gt;&lt;p&gt;Lately, I have been revisiting an idea that has been on my mind for many years:&lt;br/&gt;&#10;&lt;strong&gt;how to gradually move away from US-centric software products&lt;/strong&gt;.&lt;/p&gt;&lt;p&gt;By now, this has turned into a personal experiment —&lt;br/&gt;&#10;&lt;em&gt;part technical challenge, part entertainment, part philosophical exercise&lt;/em&gt;.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;The goal is not ideological purity, but conscious trade-offs.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;My core premise has remained unchanged over the years:&lt;br/&gt;&#10;&lt;strong&gt;minimise unnecessary data exposure&lt;/strong&gt;.&lt;br/&gt;&#10;Given the current political climate — especially developments in US politics —&#10;the topic of &lt;mark&gt;digital sovereignty&lt;/mark&gt; feels more relevant than ever.&lt;/p&gt;&lt;div style="border-left: 4px solid #888; padding: 0.8em 1em; background: #f7f7f7;"&gt;&lt;strong&gt;Working definition:&lt;/strong&gt;&lt;br/&gt;&#10;&lt;em&gt;Digital sovereignty&lt;/em&gt; means retaining control over software dependencies,&#10;data flows, and infrastructure — even if that comes at the cost of convenience.&lt;/div&gt;&#10;&lt;/section&gt;&#10;&lt;hr/&gt;&#10;&lt;section&gt;&lt;h2&gt;The Messaging Problem: Technology vs. People&lt;/h2&gt;&lt;p&gt;Several years ago, I managed to stay away from&#10;&lt;code&gt;WhatsApp&lt;/code&gt; for a surprisingly long time.&lt;br/&gt;&#10;From a purely technical perspective, this was trivial.&lt;/p&gt;&lt;p&gt;Alternatives like&#10;&lt;a href="https://signal.org" rel="noopener" target="_blank"&gt;Signal&lt;/a&gt;&#10;are feature-complete, cryptographically solid, and often superior by design.&lt;/p&gt;&lt;p&gt;The real obstacle was not software — it was&#10;&lt;strong&gt;human network effects&lt;/strong&gt;.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Most non-technical users do not care about metadata collection&lt;/li&gt;&lt;li&gt;Surveillance capitalism is abstract and invisible&lt;/li&gt;&lt;li&gt;Installing “yet another app” is perceived as friction&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;As a result, WhatsApp remains the lowest common denominator for social&#10;communication.&lt;/p&gt;&lt;div style="background: #fff3cd; padding: 1em; border: 1px solid #ffeeba;"&gt;&lt;strong&gt;Reality check:&lt;/strong&gt;&lt;br/&gt;&#10;Quitting WhatsApp is not a technical decision — it is a social one.&lt;/div&gt;&lt;p&gt;At this point, I am not willing to accept the social cost of full abstinence.&lt;br/&gt;&#10;Too many people would become reachable only via&#10;&lt;code&gt;SMS&lt;/code&gt;, &lt;code&gt;phone calls&lt;/code&gt;, or &lt;code&gt;email&lt;/code&gt;.&lt;/p&gt;&lt;/section&gt;&#10;&lt;hr/&gt;&#10;&lt;section&gt;&lt;h2&gt;GrapheneOS: A Different Baseline&lt;/h2&gt;&lt;p&gt;Instead of removing WhatsApp entirely, I decided to rethink the&#10;&lt;strong&gt;operating system layer&lt;/strong&gt;.&lt;/p&gt;&lt;p&gt;I installed&#10;&lt;a href="https://grapheneos.org" rel="noopener" target="_blank"&gt;GrapheneOS&lt;/a&gt;&#10;on my daily driver — a &lt;strong&gt;Pixel 9&lt;/strong&gt;.&lt;/p&gt;&lt;p&gt;The installation process itself is refreshingly modern:&#10;a browser-based installer, excellent documentation, and a total setup time&#10;of roughly &lt;code&gt;20 minutes&lt;/code&gt;.&lt;/p&gt;&lt;p&gt;While [GrapheneOS](https://grapheneos.org/) is still Android under the hood, it deliberately ships&#10;&lt;strong&gt;without Google Play Services&lt;/strong&gt; and without requiring&#10;a Google account.&lt;/p&gt;&lt;div style="border-left: 4px solid #444; padding: 0.8em 1em; background: #f0f0f0;"&gt;&lt;strong&gt;Key property:&lt;/strong&gt;&lt;br/&gt;&#10;Google services are optional, sandboxed, and installed per user profile —&#10;not globally.&lt;/div&gt;&lt;p&gt;There is, of course, a certain irony in the fact that GrapheneOS officially&#10;supports only Google Pixel devices — hardware built by Google itself.&lt;/p&gt;&lt;/section&gt;&#10;&lt;hr/&gt;&#10;&lt;section&gt;&lt;h2&gt;Compartmentalization with Shelter&lt;/h2&gt;&lt;p&gt;To further isolate untrusted applications, I installed&#10;&lt;a href="https://f-droid.org/packages/net.typeblog.shelter/" rel="noopener" target="_blank"&gt;Shelter&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;Shelter is essentially a user-friendly frontend for Android’s&#10;&lt;code&gt;work profile&lt;/code&gt; feature.&lt;br/&gt;&#10;It allows apps to run in a logically separate environment with strict&#10;boundaries.&lt;/p&gt;&lt;p&gt;I created a dedicated &lt;strong&gt;Work Profile&lt;/strong&gt; and moved WhatsApp into it.&lt;br/&gt;&#10;This turns WhatsApp into a semi-contained subsystem.&lt;/p&gt;&lt;h4&gt;What This Enables&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;Completely separate &lt;strong&gt;contacts database&lt;/strong&gt;&lt;/li&gt;&lt;li&gt;No implicit access to my main address book&lt;/li&gt;&lt;li&gt;GPS access denied&lt;/li&gt;&lt;li&gt;Photo library access denied&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;For now, location and media access are fully blocked.&lt;br/&gt;&#10;The experiment is to see how far usability can be stretched without&#10;completely breaking the user experience.&lt;/p&gt;&lt;/section&gt;&#10;&lt;hr/&gt;&#10;&lt;section&gt;&lt;h2&gt;Important Clarification&lt;/h2&gt;&lt;blockquote&gt;&lt;p&gt;This is not about hating WhatsApp.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;Quite the opposite.&lt;br/&gt;&#10;I genuinely enjoy WhatsApp, especially the&#10;&lt;strong&gt;Status&lt;/strong&gt; feature and its low-friction sharing model.&lt;/p&gt;&lt;p&gt;The issue is not social sharing —&#10;it is the &lt;em&gt;opaque backend machinery&lt;/em&gt;.&lt;/p&gt;&lt;p&gt;US-based cloud infrastructures, unclear data flows, and the lack of&#10;transparency around content processing are what I am increasingly&#10;unwilling to accept blindly —&#10;especially when it comes to photos of my children.&lt;/p&gt;&lt;/section&gt;&lt;p&gt;&lt;/p&gt;&lt;hr/&gt;&#10;&lt;section&gt;&lt;h2&gt;Visual Trust Boundaries: Reading the App Drawer&lt;/h2&gt;&lt;p&gt;The screenshot above illustrates how this compartmentalization manifests itself&#10;in everyday usage.&lt;br/&gt;&#10;The app drawer is effectively split into two distinct trust zones.&lt;/p&gt;&lt;p&gt;In the &lt;strong&gt;upper section&lt;/strong&gt;, you can see applications that I consider&#10;&lt;em&gt;trusted&lt;/em&gt; and therefore run in my primary user profile without additional&#10;restrictions.&lt;br/&gt;&#10;These apps have either been audited to a reasonable extent, are open source, or&#10;are sufficiently constrained in their data access patterns.&lt;/p&gt;&lt;p&gt;The &lt;strong&gt;lower section&lt;/strong&gt; contains applications that have been&#10;deliberately &lt;code&gt;crippled&lt;/code&gt; via&#10;&lt;a href="https://f-droid.org/packages/net.typeblog.shelter/" rel="noopener" target="_blank"&gt;Shelter&lt;/a&gt;.&lt;br/&gt;&#10;These apps run exclusively inside the Work Profile and are treated as&#10;&lt;strong&gt;inherently untrusted&lt;/strong&gt;.&lt;/p&gt;&lt;div style="border-left: 4px solid #b00020; padding: 0.8em 1em; background: #faf2f2;"&gt;&lt;strong&gt;Visual indicator:&lt;/strong&gt;&lt;br/&gt;&#10;Apps managed by Shelter are easy to identify.&lt;br/&gt;&#10;They are marked with a small icon depicting a&#10;&lt;em&gt;blindfolded head&lt;/em&gt; — a subtle but constant reminder that these applications&#10;are sandboxed, permission-constrained, and isolated by design.&lt;/div&gt;&lt;p&gt;This visual separation is not just cosmetic.&lt;br/&gt;&#10;It serves as a &lt;strong&gt;cognitive security cue&lt;/strong&gt;:&#10;a quick reminder of which apps operate within my trust boundary and which ones&#10;are confined to a tightly controlled execution environment.&lt;/p&gt;&lt;p&gt;Over time, this has proven surprisingly useful.&lt;br/&gt;&#10;It reinforces a mental model where applications are no longer equal peers on the&#10;system, but explicitly categorised based on&#10;&lt;code&gt;trust level&lt;/code&gt;,&#10;&lt;code&gt;data access&lt;/code&gt;,&#10;and &lt;code&gt;potential blast radius&lt;/code&gt;.&lt;/p&gt;&lt;/section&gt;&#10;&lt;section&gt;&#10;&lt;hr/&gt;&lt;h2&gt;What Comes Next&lt;/h2&gt;&lt;p&gt;This setup is still evolving.&lt;br/&gt;&#10;I will continue testing, adjusting permissions, and observing real-world&#10;limitations.&lt;/p&gt;&lt;p&gt;Expect follow-up posts on:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Push notifications and Google services in sandboxed profiles&lt;/li&gt;&lt;li&gt;Battery behaviour of work profiles&lt;/li&gt;&lt;li&gt;Long-term usability trade-offs&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;More updates will follow.&lt;/p&gt;&lt;/section&gt;&#10;&lt;/article&gt;</description></item><item><title>🚀 Mission: FreeBSD – Or How I Rage-Quit to Debian at Warp Speed</title><link>https://www.apt-upgrade.me/2025/07/11/%F0%9F%9A%80-mission-freebsd-or-how-i-rage-quit-to-debian-at-warp-speed/</link><pubDate>Fri, 11 Jul 2025 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2025/07/11/%F0%9F%9A%80-mission-freebsd-or-how-i-rage-quit-to-debian-at-warp-speed/</guid><description>&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; For years an idea had been whispering to me to finally install &lt;a href="https://www.freebsd.org/"&gt;FreeBSD&lt;/a&gt; on my tower PC. Last night I did it – and ended up in an endless boot loop. &lt;a href="https://www.ghostbsd.org/"&gt;GhostBSD&lt;/a&gt;, the friendlier offshoot, only haunted me as well. In the end I fled back to &lt;a href="https://www.debian.org/"&gt;Debian&lt;/a&gt; at warp speed, with a few thoughts in my luggage.&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;Last night, in a galaxy not that far away (namely, under my desk), I felt a sudden and powerful urge to finally install &lt;strong&gt;FreeBSD&lt;/strong&gt; on my tower PC.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Why I Never Wanted to Write *Yet Another* “Why Linux” Article — But Did It Anyway</title><link>https://www.apt-upgrade.me/2025/06/14/why-i-never-wanted-to-write-yet-another-why-linux-article-but-did-it-anyway/</link><pubDate>Sat, 14 Jun 2025 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2025/06/14/why-i-never-wanted-to-write-yet-another-why-linux-article-but-did-it-anyway/</guid><description>&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; I had sworn never to write a &amp;ldquo;why Linux&amp;rdquo; article – and here it is anyway. Not a &amp;ldquo;10 reasons&amp;rdquo; listicle, but a calm explanation of what Linux actually is, what the four freedoms of free software mean and why you really can download Linux and try it for free.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Let’s get one thing out of the way:&lt;/strong&gt; I swore I’d never write one of those posts. You know the type — &lt;em&gt;“10 reasons Linux is better than Windows!”, “Escape the walled garden!”, “Install Arch btw!”&lt;/em&gt; We’ve all seen a thousand of them. Some are great. Most… meh. But here I am — writing one anyway.&lt;/p&gt;</description></item><item><title>🧩 Jellyfin – FOSS Media Server That Plays by Your Rules</title><link>https://www.apt-upgrade.me/2025/05/25/jellyfin_foss_media_server_that_plays_by_your_rules/</link><pubDate>Sun, 25 May 2025 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2025/05/25/jellyfin_foss_media_server_that_plays_by_your_rules/</guid><description>&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; For a few days now Jellyfin has been organising my chaotic video collection on the NAS – free, open source and with the feature I value most: it remembers where I stopped. The post explains what Jellyfin is, which features it has and where its pros and cons lie.&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;ve been playing around with &lt;strong&gt;Jellyfin&lt;/strong&gt; on my NAS for a few days now, and honestly, I’m pretty happy with it so far.&lt;/p&gt;</description></item></channel></rss>