You should consider creating par2 parity files, which can repair as well as detect corrupt files.
All day long, web pages you visit will be filled with pleasing images.
Also there was the PalmOS Fossil watch (a stylus, but no keyboard).
An anonymous reader writes "Whenever I install a fresh operating system on my computer, I immediately grab a handful of programs that I simply must have.
And yet won't tell us what they are?
due to FB's policies, legitimate users feel compelled to put in fake names, birthdates, locations, schools, employers, etc.
Or in fact not put most of those in at all. Facebook is still trying to guess which continent I live on (it occasionally asks if I live in cities related to my friends list). I haven't given any info about education, work or interests (although I'm sure there's a big profile on what interests me based on what I click on).
And when you empty the vacuum, you get to breath a giant cloud dust
What are you doing? Maybe it it different for some models, but for mine, you place the end of the canister into a trash bag and pull the trigger on the handle. You can even close the base again by pushing it while it's still in the trash bag.
It then builds a database of these 'hashes'/'signatures' and can output a list of files that have a threshold of bits in common.
That's how it can ignore small changes, it loses most detail and then can ignore a threshold of differences.
It would fail if an image was cropped or rotated, for instance. It could handle picture orientation it it was modified to store 4 versions of the signature, I guess.
It won't actually remove images itself (I wrote a script to read it's output and delete listed images matching a specific path).
I needed it because Dropbox was 'fixing' orientation when it uploaded images and I wanted to clear out ones I'd backed up directly from the camera. (I usually delete duplicate images based on hash.)
I use something like this as part of my backup DATE=$(date +%C%y%m%d%H%M)
rsync --del --backup --backup-dir=../changedfiles_$DATE
The whole backup also goes to S3 glacier.
As an added step - I don't delete pictures from my camera unless they match the checksum of files in the _backup_ - not the original copy (via a script).
That way, once they're first copied from the camera, a single failure in the original, PC copy or backup copy will all result in the camera version remaining and I can check what has gone wrong.