Same bytes
This is Same bytes as last served in release caee2fb3. It changed on .
A static site is a function from one directory of files to another. If the
function is pure, the same input gives the same output, and anyone holding the
output can check it.
So every release here publishes a manifest: the sha256 of each file, in path
order. Mirror the site, run shasum -c manifest.txt, and you know
whether what reached you is what was published. The digest of that manifest is
recorded in the colophon, one line per release.
It is a small claim, and mostly it protects me from myself: a broken template,
a stray file, a deploy that quietly kept serving last week. But it also means the
history here can be checked instead of trusted. A date on a page is worth what
the person who typed it is worth. A manifest that archives elsewhere picked up on
the day it was published is worth a little more.