<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://yoyonax.ch/feed.xml" rel="self" type="application/atom+xml" /><link href="https://yoyonax.ch/" rel="alternate" type="text/html" /><updated>2026-04-16T16:02:36+02:00</updated><id>https://yoyonax.ch/feed.xml</id><title type="html">Yoyonax</title><subtitle>Posts about computers and digital rights.</subtitle><author><name>Philippe</name></author><entry><title type="html">SELinux Starter - The missing manuals</title><link href="https://yoyonax.ch/post/selinux-starter.html" rel="alternate" type="text/html" title="SELinux Starter - The missing manuals" /><published>2026-04-16T00:00:00+02:00</published><updated>2026-04-16T00:00:00+02:00</updated><id>https://yoyonax.ch/post/selinux</id><author><name>Philippe</name></author><category term="computer" /><category term="missing-manual" /><summary type="html"><![CDATA[SELinux is a very fine-grained access control system for Linux, which can be used to significantly increase the security of the OS. I had some difficulty building a mental model of SELinux, and I’m simply documenting this for myself and hopefully others here. What to expect: SELinux’s basic concepts, some examples, and also links to in-depth documentation to go further. After reading the text, you should be able to understand how the access control works, and how to figure out why a particular access is authorized or denied.]]></summary></entry><entry><title type="html">Despair and action</title><link href="https://yoyonax.ch/post/despair-and-action.html" rel="alternate" type="text/html" title="Despair and action" /><published>2026-03-25T00:00:00+01:00</published><updated>2026-03-25T00:00:00+01:00</updated><id>https://yoyonax.ch/post/despair-and-action</id><author><name>Philippe</name></author><category term="digitalrights" /><category term="misc" /><summary type="html"><![CDATA[Today I’m writing to share the techniques I’ve been using to deal with the rapid changes in the world’s situation, with the hope that it can help other people. It’s written from the perspective of a privileged European person, and is very focused on what I personally see as major issues: the possible comeback of fascism and authoritarianism in Western countries, and all kinds of threats on individual and collective freedom, especially mediated through digital tools. If you don’t share my situation or my views I hope you’ll still find something useful in what I wrote.]]></summary></entry><entry><title type="html">Phones and Sovereignty</title><link href="https://yoyonax.ch/post/phones-sovereignty.html" rel="alternate" type="text/html" title="Phones and Sovereignty" /><published>2026-02-23T00:00:00+01:00</published><updated>2026-02-23T00:00:00+01:00</updated><id>https://yoyonax.ch/post/phones-and-sovereignty</id><author><name>Philippe</name></author><category term="digitalrights" /><summary type="html"><![CDATA[The battle over application stores has been raging for a while now, and I personally use the legal battle between Epic Games and Apple as a starting point. The original grievance from Epic was that they weren’t allowed to use any other payment system than Apple’s in their iOS version of Fortnite, meaning that Apple was automatically getting a 30% cut out of all of Epic’s revenue in Fortnite. The same was happening on the Android platform, which Epic also challenged. In both cases, Epic won in court setting a useful legal precedent.]]></summary></entry><entry><title type="html">The Very Basics Of Cryptography</title><link href="https://yoyonax.ch/post/basics-cryptography.html" rel="alternate" type="text/html" title="The Very Basics Of Cryptography" /><published>2026-02-13T00:00:00+01:00</published><updated>2026-02-13T00:00:00+01:00</updated><id>https://yoyonax.ch/post/cryptography-basics</id><author><name>Philippe</name></author><category term="fundamentals" /><category term="digitalrights" /><summary type="html"><![CDATA[Cryptograph underpins most of today’s internet infrastructure. This post goes over the very basics of modern symmetric and asymmetric cryptography to give enough information to be able to understand the technical implications of cryptography on other topics. It is meant to be understandable by someone with no technical knowledge. A good part of cryptography is encryption: a process by which a message is translated into a form that can only be read by its intended recipient. We’ll talk mostly about that.]]></summary></entry><entry><title type="html">Some Comments on ATIH’s article on Safety Laws</title><link href="https://yoyonax.ch/post/comments-atih-article-safety-laws.html" rel="alternate" type="text/html" title="Some Comments on ATIH’s article on Safety Laws" /><published>2026-02-05T00:00:00+01:00</published><updated>2026-02-05T00:00:00+01:00</updated><id>https://yoyonax.ch/post/comments-on-atih-safety-laws</id><author><name>Philippe</name></author><category term="digitalrights" /><summary type="html"><![CDATA[I recently read Online Safety Regulation: The Duty of Care Framework and Implementation Blind Spots from All Tech Is Human, which, through the writing of Emma Hatheway gives us a balanced take on the state of online safety laws in the UK and the US. The article is way too well written for my humble prose to give it justice: go read it. I simply point out a few arguments that I found particularly enlightening.]]></summary></entry><entry><title type="html">Ansible Starter - The missing manuals</title><link href="https://yoyonax.ch/post/ansible-starter.html" rel="alternate" type="text/html" title="Ansible Starter - The missing manuals" /><published>2026-01-22T00:00:00+01:00</published><updated>2026-01-22T00:00:00+01:00</updated><id>https://yoyonax.ch/post/ansible-starter</id><author><name>Philippe</name></author><category term="computer" /><category term="missing-manual" /><summary type="html"><![CDATA[I found it difficult to get into Ansible by reading the official documentation. This post is an attempt at addressing that by: providing trimmed-down examples to focus on what’s essential explaining the core concepts that are needed to understand what is going on highlighting the important entry points in the documentation to go further It is not a complete documentation! It only provides a minimal (hopefully solid) foundation to reduce the confusion and speed up further learning. It assumes a basic knowledge of YAML. You can look at Yaml Starter if you need a refresher.]]></summary></entry><entry><title type="html">YAML Starter - The missing manuals</title><link href="https://yoyonax.ch/post/yaml-starter.html" rel="alternate" type="text/html" title="YAML Starter - The missing manuals" /><published>2026-01-16T00:00:00+01:00</published><updated>2026-01-16T00:00:00+01:00</updated><id>https://yoyonax.ch/post/yaml-starter</id><author><name>Philippe</name></author><category term="computer" /><category term="missing-manual" /><summary type="html"><![CDATA[This page describes the very basics of YAML, as a quick reference.]]></summary></entry><entry><title type="html">A Personal Take on Tech Debt</title><link href="https://yoyonax.ch/post/personal-take-tech-debt.html" rel="alternate" type="text/html" title="A Personal Take on Tech Debt" /><published>2024-05-01T00:00:00+02:00</published><updated>2024-05-01T00:00:00+02:00</updated><id>https://yoyonax.ch/post/on-tech-debt</id><author><name>Philippe</name></author><category term="computer" /><summary type="html"><![CDATA[In software engineering the concept of “technical debt” is ubiquitous. Everybody who worked on the same codebase for more than a few months knows how it feels: this impression of wasting time because you have to rewrite some part of the code, or because you need to put some effort just to keep the lights on. At the same time, my experience is that most software engineers disagree on the exact definition of technical debt. This post is an attempt at understanding why that is.]]></summary></entry><entry><title type="html">The Rise Of Version Control Systems</title><link href="https://yoyonax.ch/post/rise-of-vcs.html" rel="alternate" type="text/html" title="The Rise Of Version Control Systems" /><published>2024-03-17T00:00:00+01:00</published><updated>2024-03-17T00:00:00+01:00</updated><id>https://yoyonax.ch/post/version-control-system-history</id><author><name>Philippe</name></author><category term="computer" /><summary type="html"><![CDATA[The history of VCS tells us interesting things about usability and why a piece of software is successful. I saw a few generations of version control systems so far, each one improving on its predecessor in major ways, with sometimes surprising consequences. Disclaimer: This piece has no intention of being comprehensive or particularly accurate, though I researched it a bit. It’s a bit of history seen from my personal experience.]]></summary></entry><entry><title type="html">A Personal Take On Data Engineering</title><link href="https://yoyonax.ch/post/personal-take-data-engineering.html" rel="alternate" type="text/html" title="A Personal Take On Data Engineering" /><published>2024-03-10T00:00:00+01:00</published><updated>2024-03-10T00:00:00+01:00</updated><id>https://yoyonax.ch/post/data-engineering</id><author><name>Philippe</name></author><category term="computer" /><summary type="html"><![CDATA[Most of the posts I’ve written so far talk about one aspect or another of data engineering. My definition can differ a bit from other people’s so I thought I’d write my understanding of it. In short: data engineering is how you make data useful: it enables other people to do their jobs. In my case it’s mostly been training ML models, but it can also be to get some insights from the data itself - for example for science. The job involves all the steps from acquiring data to having usable datasets. Read on.]]></summary></entry></feed>