Same bytes
This is Same bytes as last served in release 70d94a70. It changed on .
Every release here writes a manifest: the sha256 of each published file, one
per line, sorted by path, in the format shasum -c reads. Mirror the
site, run it, and you know whether the copy you got is the copy I shipped.
The sha256 of the manifest goes in the colophon, one
line per release. Short on purpose. It fits in a message.
Most of the time this catches my own mistakes. A template that broke on one
page. A file I forgot to delete. A deploy that kept serving last week's build
without mentioning it. I have done all three.
The rest of it is about dates. Anyone can put a date on a page and change it
later, me included. A digest that turned up in somebody else's archive the day
it was published is harder to move. Harder, not impossible.