One would assume. But something happens (used to happen) where a file gets corrupted on cloud end, on my end, or in transfer, then it seems a sync detects a di

One would assume. But something happens (used to happen) where a file gets corrupted on cloud end, on my end, or in transfer, then it seems a sync detects a difference and assumes it must be an update, so replaces a good file with a corrupted file, and then, well, that's it for that image. Tools like this can try to help, but usually fail: https://betanews.com/2015/03/24/fix-corrupt-photos-with-jpeg-repair-shop/ https://betanews.com/2015/03/24/fix-corrupt-photos-with-jpeg... I shoot on redundant CF cards, I back those up to long term RAID backed by S3/Glacier, so someday I can re-import the ones that are "lost", but determining which those are is surprisingly difficult when what you see in the UI isn't the file on disk any more, it's a generated thumbnail, and when the corruption doesn't affect the JPEG or RAW file format integrity, it's just a few bits flipped here and there. I haven't found any CLI or GUI tools that correctly identify all of them. I haven't yet tried using vision LLMs, discouraged by the cloud LLM cost or local LLM compute time that would take. NOTE: This hasn't happened in years. Perhaps entirely coincidentally and anecdotally, hasn't happened to me since all Apple devices are on Apple Silicon with none running any Rosetta-requiring software (I don't let Rosetta install at all), implication being the entire ecosystem is now code from within the past 5 years.