nspire the digital elder's logbook

This entire site is one file. Everything you need lives in the source at your feet: styles inline, behaviour inline, content inline. There are deliberately no dependencies, because a personal archive should not expire when somebody stops maintaining an npm package.

The model is simple: each entry below is an <article> tagged with a media era and a type. The eras map my biography — vinyl childhood, tape-and-CD youth, the dotcom years, now the AI age. To publish, copy any article block, paste it above the newest one, adjust its tags and date, and save. Full instructions sit in the HTML comments at the top of the file.

Security posture is deliberately strict: the Content Security Policy here permits nothing external — no scripts from anywhere else, no images fetched over the wire, no network connections at all. That leaves roughly zero attack surface for a static page. It degrades gracefully too: if JavaScript never runs on your device, every post still reads fine; filtering and RSS export simply switch themselves off.

(The entries that follow are demonstration seed posts, written to feel right until I replace them with the real thing.)

A few days ago I pointed my browser at an address I built websites under in my formative years. The server answered with a bare 403 Forbidden — a door locked since around 2014. That felt wrong. Not because it should be busy, but because a piece of my history had quietly become dead air.

So this is the act of taking it back: not for traffic, not for metrics, but as a place where my own thinking has room to sit. Every era of technology I've lived through tells me one thing — the formats change, the habit of writing things down survives.

I was born at the very start of the eighties, which means my first music came from vinyl and magnetic tape. There was ceremony in it: dust off the record, set the stylus, watch it lower with that particular click. Tape had its own ritual — the clatter of the cassette deck, the satisfying thunk of the door closing.

Nobody thinks about the ceremony anymore because there isn't one. A track streams and starts; nothing lowers onto anything. I'm not mourning that — I love what digital audio did to my world — but I've started noticing the little rituals we lose without naming them. This page is partly an attempt to remember what they were for.

A small invention log: I finally built a proper capture chain for digitising the tape collection before it degrades further. The signal path matters more than people expect — a decent preamp, a line-level input with headroom to spare, and software that records at 24-bit before any dithering gets a vote.

The first pass came out hissy; the second taught me that azimuth on the deck was off by a hair. There's a lovely moment in this hobby where an old physical medium meets modern measurement tools and the two actually agree about what the original performance sounded like. That is, in miniature, exactly why I still enjoy engineering.

Through the dotcom boom I ran web development from this domain. Hosting back then wasn't renting a button on a dashboard — it was knowing which box held your site, restarting a service at 3am, and explaining to clients why their "website" was really a directory of files with very particular opinions about permissions.

The whole industry has moved on precisely because people like us made that chaos boring and reliable. Somewhere along the way we stopped being wizards and became infrastructure. I'm not sure that's a loss — but I am sure someone ought to keep the receipts for what it used to be like.

As someone who spent decades making computers do exactly what I told them, watching one learn to hold a conversation is equal parts exhilarating and unsettling. My security training keeps insisting every new capability needs a boundary; my engineer's instinct keeps wanting to take it apart.

The honest field note is this: the most useful posture isn't awe or panic, it's auditability. Know what something was asked to do, know what it did, and make sure you can unwind either one. The same discipline that kept servers alive in the dotcom years turns out to be the right frame for the AI age. Some things don't change when they look like they're changing everything.