I wanted to find all the duplicate images on my machine and instead

did you write it in 30 seconds or does it accomplish its task in 30 seconds
your post was very vaguely written and now i'm confused, so i'll assume your software is written in the same fashion
typical freetard garbage...

>>61530061
it takes less than 10 seconds to actually read the command and figure it out
typical wintard brainlet

File: 1403180946565.jpg (72KB, 621x621px) Image search: [Google]

72KB, 621x621px

>>61529736
>.txt
Also, what about slight variants of the same image?

>>61530232
exact image duplicates are good enough
I found 1853.

my solution uses findimagedupes and eye of gnome to go through the similar enough images.

Feels good. Just wrote one to extract folder full of archives of various types each into its own folder.

>>61529736
>detecting image similarity in current year
>uses md5
>ignores perceptual hashes, which would have made his software better
why are you so fucking retarded?

>>61530156
Stay trolled, angry retard.

>>61529736
Every single one of those commands requires you to memorize it's options and you're even using xargs to make up for unix's arbitrary limit on argument count.

How many years of maintenancing your computer as a goddamn hobby does it take to reach this level of comfort with the command line?

>>61530466
t. Brainlet

Different bash lover here.
>Every single one of those commands requires you to memorize it's options
You're not supposed to memorise options. It's enough to know where to look them up.

$ man command

>>61530466
>you're even using xargs to make up for unix's arbitrary limit on argument count.

$ md5sum * | sort | uniq -Dw 32 > /tmp/dupes.txt

Works on my machine™