Roos Maas

Update 70: If you still roll a 1024-bit KSK in 2026 I need you to sit down for a minute.

Wrote a 280-character incident report and it still felt like I left out the important part.

That matches what I saw. Timestamp even lines up. [52.1]

Update 114: Espresso in Muiden tasted like someone finally cleaned the group head. Small civic miracle.

That matches what I saw. Timestamp even lines up. [27.1]

Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [52.2]

Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [27.2]

Update 72: Office rumor mill says the staging TLS cert expires on a Friday. Of course it does.

Update 115: The construction on the way to Zeewolde has entered its third personality. Today it is a labyrinth.

Do you have a ticket number? The public status page is lagging again. [52.3]

Do you have a ticket number? The public status page is lagging again. [27.3]

I can bring a folding table if we are still on for Amersfoort. [52.4]

The 07:12 to Lelystad was on time. I do not know how to process this emotionally.

Update 73: Tried the long way around Maastricht on the bike. Extra twelve minutes, minus two close calls.

Update 116: Self-hosting update: the backup ran. The restore drill did not. Guess what I am doing tonight.

The Amersfoort version of this story is even weirder. (73)

Stopped using a CDN in front of a static site. Latency went up, bills and mystery headers went down.

Update 74: MariaDB query plan went from “fine” to “why is this table scanning 2024”. Indexes are a lifestyle.

On it. I will check the probe from Scheveningen when I am home. [13.1]

Found a bench in Zwolle that is not next to a speaker. I am not telling you which one.