mkj

That was edited in later

59 seconds will still have second alignment. Maybe it needs to be prime milliseconds or microseconds.

Fuzzing doesn't tend to catch overflow cases since operations aren't repeated enough times. I wonder if fuzz engines could add a "counter detection" pass that reruns inputs that are seen to increment values. Maybe that's already been tried by someone.

dmesg

Maybe you could report it as a normal bug report, by hand?

Unless the field of software development somehow totally stagnates, I'm confident that at some point I will move to a different hosting service, as github goes the way of sourceforge, travis-ci, and myspace. So my personal domain will continue to be relevant (it's lasted fine 23 years).

Maybe at that point it won't be using git either, or maybe it will - who knows.

Could you read it with a flatbed scanner or other photography? That should be unobtrusive.

I guess it was just part of the current website generation's training set!

These don't seem really physically immutable, just protected by the firmware of the drives/robot against being written twice. With enough effort couldn't the same laser write _something_ over them again? Maybe optical discs need a hole that gets punched out or something, like the old floppy disk write protect. (And then make that control a physical laser power switch)

So Google Pics is for work, and Google Photos is for personal photos? Got it.