I prefer DSC009847.JPG.b3sum sidecar files [1] or per-directory checksum files like B3SUMS because they can be verified with standard tools. This scheme

I prefer DSC009847.JPG.b3sum sidecar files [1] or per-directory checksum files like B3SUMS because they can be verified with standard tools. This scheme also allows you to checksum files whose names you can't or don't want to change. (Though in that situation you have an alternative of using a symlink for either the original name or the name with the checksum.) I have used the scheme less since I adopted ZFS. I do use very similar example.com/foo/bar/b3-abcd0123.html for https://example.com/foo/bar https://example.com/foo/bar in the archival tool for outgoing links on my website. It avoids the need to have a date prefix like in the Wayback Machine while preventing duplication. Speaking of .iso files. A recent PR [2] to my favorite Linux USB-disk-image burning tool Caligula has added support for detecting and verifying sidecar files like foo.iso.sha256 (albeit not Blake). [1] https://en.wikipedia.org/wiki/Sidecar_file https://en.wikipedia.org/wiki/Sidecar_file [2] https://github.com/ifd3f/caligula/pull/186 https://github.com/ifd3f/caligula/pull/186