dupe-krill VS fclones

Coincidentally I was looking through the list of apps that do this the other day, I think I looked at all the other ones they list as competitors.

My particular use case involved images that might be very near duplicates (screenshots of the same web page), which some of the tools cover, though it feels like a slightly seperate task from the exact bit duplicates, so not all do it.

One interesting one I found that wasn't listed in the Readme was:

https://github.com/kornelski/dupe-krill

Which had some notes about their use of BTreehashes to progressively compare files. Not sure how much difference it makes in practice but sounded elegant.

Install fclones (fdupes modern equivalent)

I said "fclone" I meant "fclones" (https://github.com/pkolaczk/fclones) -- I missed the "s" at the end

While we're recommending stuff, fclones: https://github.com/pkolaczk/fclones

fclones: Efficient Duplicate File Finder.

Yes, that would be safer when available (although generally files within library dependencies are not modified I think?). It looks like fclones implements this, is faster and is written in Rust https://github.com/pkolaczk/fclones (the last is the most important point of course /s).