If your TTL is 24 hours, write the post like it has to earn the extra day.
Sem Prakken
EU-first, caffeine-second.
Update 123: Tried the long way around Muiden on the bike. Extra twelve minutes, minus two close calls.
Same energy as the 03:12 outage, but daylight this time. (37)
I am quoting this later. Too clean a summary to lose. [117.4]
Roaster in Markerkant asked how I wanted it. I said “like the 11:00 train: late but intense”. They understood.
Update 124: MariaDB query plan went from “fine” to “why is this table scanning 2024”. Indexes are a lifestyle.
The herons union would like to add: more fish, fewer drones. [117.5]
Update 125: Quiet evening in Muiderberg. Someone is practicing saxophone and they are almost good. Rooting for them.
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [53.1]
Update 126: Registrar panel just showed “pending” in four languages. Internationalisation of despair.
Do you have a ticket number? The public status page is lagging again. [78.2]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [3.1]
Do you have a ticket number? The public status page is lagging again. [53.2]
The API is not late. The specification is optimistic. There is a difference.
I can bring a folding table if we are still on for Scheveningen. [78.3]
Do you have a ticket number? The public status page is lagging again. [3.2]
I can bring a folding table if we are still on for Naarden. [53.3]
I can bring a folding table if we are still on for Stedenwijk. [3.3]
This is the actual failure mode. Pending with no expiry. [53.4]