More about checking the integrity of files on macOS, with a new version of a free utility, news of the next apps, and error-correcting code perhaps?
storage
To check the integrity of important documents, we’re going to calculate their SHA256 digests. But where should those be stored if HFS+ and APFS don’t have a suitable attribute?
If macOS can’t do it, how should we check the integrity of important files? Use a checksum, or a hash function? And which?
We take for granted that our files remain uncorrupted, but know that isn’t always true. How can we fix or even detect such changes?
First release version, for El Capitan to Catalina. And completely free of course.
Other major changes include detailed reporting, and user control over the size of buffer used, bringing big performance improvements.
How can you tell whether the file you see in storage today is the same as it was a year ago when you last opened it?
Over time, stored data gets gradually corrupted. But over what period – months, years or centuries? And at what rate?
What do you do with all those old but important documents? Do you just leave them cluttering up storage, or have you archived them? Here’s how to archive properly.
The fine line between precision and obscurity examined in the Finder, against Apple’s Style Guide, and its accuracy. And what does HD stand for?
The Eclectic Light Company 