Technology Commentary

Do note that this is a slightly sarcastic post, there is alot of sarcasm on the internet at the moment. Take a moment to reflect if you want to expose yourself to more sarcasm. There are plenty of …

Firstyear's blog

My client was a utility company, and they had a big problem...

Reading the tea leaves

This was published in English (and Polish) in 1986 under the title One Human Minute: So it was not humanoid automata that former the new armies but synthetic insects (synsects) — ceramic microcrustacea, titanium annelids, and flying pseudo-hymenoptera with nerve centers made of arsenic compounds and with stingers of heavy, fissionable elements…The flying synsect combined […]

I spend a lot of time thinking about the open web. We talk about it a lot. But I'm not sure it exists, at least not in the way it's often described. Embedded within the underlying architecture of the web is an ideal of openness. One can publish anything and one can link to anything.

Thoughts about how our feed readers homogenize the web

I use AI for some things. I’m putting that out there right from the start because it will get rid of those people who are so unreasonable that they can’t even be arsed to hear me out. I get most of the arguments against “Artificial Intelligence”. In fact, I agree with a lot of them. From the environmental and human costs to the apocalyptic possibilities, the arguments make a lot of sense. There are a lot of dangers when it comes to this “AI” revolution, and the corporations who are in charge of this revolution cannot be trusted to do anything but try to pad their bottom line.

The determination to move away from the addictive doom-scrolling of social media has given me pause, given me space to look around at how I use the internet and figure out where I get most value an…

A guide on engaging nuanced topics of conversation

I’ve always been quietly impressed by those who can grasp an idea, hold it deeply, and communicate it clearly to others, building the passion they have for something into a drive and commitment to …

Roy Tang's blog. Programmer, engineer, scientist, critic, gamer, dreamer, and kid-at-heart. Randomly amazed.

The web is mind-bogglingly huge; let's look at how personal websites can thrive and interact despite that.

Just as it’s still possible (though seldom necessary) to ride a horse, it is still possible to surf the internet. It’s a thrill not yet lost to time.

The demo to Production Death ValleyIf you've worked on an AI feature, you know the feeling. You start building something that you are excited about, set

By letting Muddy Waters hear himself for the first time, he unlocked a new confidence that set the sharecropper on the path to superstardom. And that’s just the start of what he found in churches, prisons and even lumberjack camps

Read and watch Jeffrey Martin's presentation from 3Dise 2026- The World at Eye Level: Mapping at Human Scale to Solve AGI

A 5 min crash course!

Why your best architectural instincts are slowing you down

Dedicated to the advancement of layer 2 irresponsibility.

An institutional notice regarding the application of Amazon Web Services and the Society's findings. –

An observation on the parallels between the American resistance to the metric system and the American resistance to IPv6. –

Both sides are grappling with a real existential threat, and both sides feel like they are screaming into the void. Here's how to close the gap and get everyone pulling in the same direction.

Safari and Firefox change how big sites render based on the domain. TikTok, Netflix, Instagram… even SeatGuru. Chrome doesn’t. Why is that?

Mystery of GPS interference across Europe raises questions about Russian motives.

Six years ago, I nearly got my ISP to upgrade our fibre connection to 1Gbps. As I said at the time: This is a curmudgeonly post which is going to look ridiculously outdated in a few years. What's the point of Gigabit broadband? Well, it's a few years later and Virgin Media have just given me their Gig1 package for £30 per month. Nice! With all the inflation related price rises, it's great to …

IT Philosophy, the first of three on European software sovereignty. A great deal of procurement language at the moment treats open source as a sovereignty answer; the reasoning runs that proprietary cloud providers are foreign-jurisdiction firms, open source is by contrast open, therefore open source is sovereign. The conclusion is louder than the premises warrant. Open and owned are not the same word; they overlap in places, they diverge in others, and where they diverge tends to be precisely where procurement assumes they do not. The question is being asked across multiple jurisdictions: France's Interministerial Digital Directorate (DINUM) announced in April 2026 a migration of its own workstations from Windows to Linux, with a directive to all ministries to formalise plans for eliminating extra-European dependencies by autumn; Huawei launched its HarmonyOS PC line in May 2025 after the company's Windows licence was withdrawn under US sanctions; India has produced BharOS through IIT Madras and government sponsorship; China's procurement directives now favour domestic ISA work at the chip layer. A licence is not a deed of ownership, it is a statement of conditions. The licence landscape needs three shelves rather than two. Permissive licences (BSD 2-Clause, BSD 3-Clause, MIT, Apache 2.0) let anyone build on the code, fork it, ship it, sell it and combine it with other code under any licence at all; original authors retain attribution. Copyleft licences (GPLv2, GPLv3, LGPL) let anyone receive and modify the code but require that any distribution of the modified version arrives under the same licence; the receiver does not own what they build with it in the unrestricted sense, they hold it under the conditions the original author set, in perpetuity. Network copyleft licences (AGPLv3) extend copyleft to the case where the modified version runs as a service rather than being distributed as a binary; Section 13 closes what is sometimes called the SaaS loophole of classical GPL. The Server Side Public Licence (SSPL), introduced by MongoDB in 2018 and adopted by Elastic in 2021, extends AGPL's network clause to require open-sourcing of the entire surrounding management stack; the Open Source Initiative declines to recognise SSPL as open source, citing field-of-use discrimination, so SSPL is a fourth shelf that does not behave like the other three. The European Union Public Licence (EUPL-1.2) sits in the copyleft family and is OSI-approved; it exists in part because the EU wanted a Union-grounded licence with cross-Member-State legal certainty in twenty-three languages. GPL keeps the code open, it does not return it to the receiver: every downstream version remains under GPL, the original author's licensing choice propagates indefinitely, and a European entity that needs to take a piece of GPL code and integrate it with proprietary or commercially-sensitive surrounding code finds that GPL has decided the licensing of the surrounding code as well, because the licence absorbs. A useful demonstration is FreeBSD's compiler migration: FreeBSD 10.0 (January 2014) moved its base system from GCC to Clang; the technical case existed but was not decisive, the decisive factor was that GCC had moved to GPLv3 and a coherent permissive base could not host a copyleft compiler whose conditions would leak outwards. AGPL is the honest middle: if you modify this code and use it to serve users over a network, the users have a right to your modifications; it does not require you to share user data, internal management software, or anything outside the modified program itself, which is exactly what tipped SSPL out of the OSI classification. The xz incident reminds us that open is not audited: in March 2024 a Microsoft engineer named Andres Freund was profiling SSH connections, noticed unusual CPU time inside liblzma, and discovered a backdoor (CVE-2024-3094, CVSS 10.0) inserted by a maintainer operating under the name Jia Tan after a multi-year social-engineering campaign that began in 2021; the backdoor was discovered by one person's curiosity, not by the audit infrastructure of the open-source ecosystem, because permissive licensing makes audit possible, it does not make audit happen. In October 2024 the Linux kernel project removed approximately eleven maintainers from a particular jurisdiction subject to expanded US sanctions; the change appeared on the kernel mailing list as compliance requirements, Linus Torvalds confirmed it shortly afterwards and declined to reverse it; the specific jurisdiction is not the point, the point is that the Linux Foundation is registered in the United States and US sanctions reach the operations of US-registered organisations, so whichever jurisdiction comes under expanded US legal pressure next has the same exposure to the same mechanism. The CLOUD Act (March 2018) permits US law enforcement to compel US-based service providers to hand over data regardless of where that data is stored; Schrems II (Court of Justice of the European Union, Case C-311/18, July 2020) held that US surveillance law under FISA Section 702 and Executive Order 12333 does not meet the proportionality standard required by EU law and invalidated the EU-US Privacy Shield. These create a strong reason for European public services to prefer software stacks they can host, modify and audit locally; the same reasoning runs in Beijing, in New Delhi, in Moscow, in Brasilia, with the relevant counterpart jurisdiction differing in each case. A licence is a permission slip; sovereignty is the practice of using the permission, which consists of reproducible local build, audit and signing, and continuous re-receipt. A receiver who owns the licence but does not own the build infrastructure does not own the result; a receiver who owns the build infrastructure but runs it on someone else's silicon has only moved the question down a layer. This piece sets the question; the architectural layer is next Sunday, the silicon layer the Sunday after.