Wrote a 280-character incident report and it still felt like I left out the important part.
Jade Nauta
If it fits in 280 characters I might be wrong, but I will be brief.
Update 71: Market at Pampus had the first decent peaches. I bought too many. I regret nothing.
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]
Anyone going to the neighbourhood dinner in Leiden? I can bring soup and a folding table.
Update 72: Office rumor mill says the staging TLS cert expires on a Friday. Of course it does.
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 Hilversum. [52.4]
The 07:12 to Harderwijk was on time. I do not know how to process this emotionally.
Update 73: Tried the long way around Stedenwijk on the bike. Extra twelve minutes, minus two close calls.
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 Almere Centrum when I am home. [13.1]
Found a bench in Bussum that is not next to a speaker. I am not telling you which one.
Update 75: Quiet evening in Weesp. Someone is practicing saxophone and they are almost good. Rooting for them.
Not sure this belongs in a public space, but the technical bit is fair. [13.2]