Posts on Siryu

CI for a Decentralized Forge: Why I Ended Up Bridging Radicle and Tekton

Thu, 09 Jul 2026 19:00:00 +0200

A few months ago I wrote about GitHub’s independence — short version, migrating from one centralized forge to another isn’t a strategy, it’s a rebrand. Recently I followed up with a review of Euro-Office and LaSuite, making the same point about European “sovereign” office suites being developed on GitHub. At the end of that article I promised I’d come back to this topic soon.

Here we are. This first post is about the why: why CI matters even when you’ve moved your git off the mainstream forges, why decentralizing CI is harder than decentralizing storage, and how I ended up picking Tekton after looking at some alternatives. The nuts and bolts of how the Radicle broker, my adapter, and the Tekton cluster talk to each other are worth their own write-up, and I’ll probably come back to them once the setup has more mileage.

Euro-Office and LaSuite: European Sovereignty Built on American Ground

Sat, 04 Jul 2026 15:30:00 +0200

A quick follow-up to my previous piece on USA lock-in. That article ended on a call to action: Europe needs to stop building on American infrastructure, and the smartest path forward is public investment in open-source foundations. Since then, two projects have caught my eye — one federal, one industry-led — and both prove that Europe is moving, and that the momentum is real. They also, unfortunately, prove that the reflex to build sovereign tools on top of the very platforms we’re trying to escape is still with us.

The USA Lock-In: When Tech Dependency Becomes Geopolitical Vulnerability

Mon, 19 Jan 2026 11:12:13 +0100

I often say that “everything is political,” and I’ve never been able to fully separate tech from politics—this article is no exception. I promise I’ll try to publish more purely technical posts soon, but in the current context, it’s hard to focus on anything else. For context: I’m French, and this perspective comes from someone watching the United States from outside its borders.

I won’t dwell on the current president’s domestic policies—despite the tragedy unfolding for many American citizens, that’s not the focus here. However, Umberto Eco’s checklist in “Ur-Fascism”¹ seems pretty well checked… But let’s examine the recent geopolitical events and decisions:

GitHub's Independence: A Cautionary Tale of Open Source in a Capitalist World

Thu, 21 Aug 2025 17:12:29 +0200

The recent departure of Thomas Dohmke from GitHub has created significant discussion within the tech community. As the former CEO, Dohmke was seen by many as a steady hand navigating GitHub’s post-acquisition era under Microsoft. His exit has reignited a critical debate that has simmered for years: Can a single, corporate-controlled platform ever truly serve as the unshakeable foundation for the entire open-source world?

In response, we’re seeing familiar calls to action—to migrate to platforms like GitLab or Gitea. While these are great alternatives, they risk repeating the same cycle. The core issue isn’t where we go next, but the fundamental problem of centralization. A new “Eldorado” will emerge, grow in value, get acquired, and inevitably, its licenses and terms of service will change. The real problem isn’t GitHub’s ownership, but the systemic risk that comes with placing our collective code in a single, vulnerable silo.

Was it worth to read that ?

Mon, 17 Mar 2025 10:48:55 +0100

I had originally written a post about a tool I use daily, but as I was writing it, I realized how little value it actually brought…
Don’t get me wrong—I still plan to publish it. But during my review, I had the horrible feeling that I had wasted my time reading it.
Trying to understand why this article lacked interest, I took some time to read other articles I had recently come across—some that I really enjoyed, and others that gave me the same empty feeling as the one I had just written.

Abstraction Hell

Thu, 20 Feb 2025 21:38:49 +0100

Cloud is just someone else computer

If you work or are interested in information technology (IT), you’ve probably seen this joke on memes, shirt and mugs… In fact it’s quite far from reality, your implementation of an Infrastructure as Code (IaC) abstraction involves someone else’s API, which calls various services from your cloud providers; these services, in turn, deploy applications developed by someone else running on someone else’s computer. I’ve vonlountrily shortenthis sentence before it became too long but you got my point.