Colophon

How this site is built, and what it does with your data. The short answer to the latter is "as little as possible".

Typeface: Berkeley Mono (TX-02), from U.S. Graphics Company.
Markup: CommonMark Markdown plus HTML layout templates and CSS, mostly edited by hand. No framework.
Server: An Alpine Linux server running nginx.

Tooling : A static site generator I wrote from scratch converts everything to modern HTML, creates AVIFs and thumbnails from source images and deploys the site. A separate script handles initial server provisioning.

Accessibility

I have done my best to make sure everything I do on this site is accessible to all users. However, I do not personally use any assistive technology, and I know I may miss accessibility problems. If you encounter an accessibility issue on the site, please email me and I will do what I can to fix it.

Size

I've put a lot of work into keeping this site as lightweight as possible without compromising the design. This is accomplished by keeping the HTML generation under my full control so that I know exactly what each Markdown input will produce, providing AVIF encoded images where suitable (film photos in the photography section are JPEG-only because AVIF wipes out the film grain at any setting that results in a size savings), and using absolutely no JavaScript at all except for a single page with a YouTube video embed.

On first load of the site index, the font file at ~158k is overwhelmingly the largest component of the page. After that is cached, image downloads (anywhere from ~100k each for project-page AVIFs to ~1MB each for film photo plates) are the overwhelming majority of bytes transferred.

AI

I don't like the legal implications of how AI companies have stolen the world's data, but the resulting tools are incredibly useful. While I wouldn't say I lack principles, they do at some point yield to practicality.See also: my occasional use of Uber/Lyft and refusal of any implication that individual action will ever measurably impact climate change I use LLMs for debugging, prototyping, exploration of ideas and proofreading. I do not use them to write prose, and I do not use them to write code I care about. For proofreading tasks, I ask for feedback. I decide what to change based on that feedback, and make the edits myself.

No directly visible part of this site or any of the projects presented on it is AI written. The only behind-the-scenes exception is all of the site CSS, which as far as I'm concerned is black magic that no human should try to comprehend, but my hope is to get around to organizing it and re-writing it into a more modular form so that the site generator can include only what specific pages need soon (tm).

Privacy

No JavaScript, no cookies, no tracking pixels. Fonts, stylesheets and photos are all hosted on this server.

The server does keep access logs, including IP addresses, requested URLs, and browser information. I use them to see whether anyone is reading. I don't share them.

Copyright

For substantial pieces of code, I link to a repository with its own license, which sets the terms for reuse. Any code snippet that doesn't come with a project repository link I consider too trivial to be copyrightable, but you should talk to a lawyer rather than take my word for it.