jdupes (as opposed to fdupes)

[paxmark1]

I never heard of it before.  but   
https://forum.siduction.org/index.php?topic=8100.msg65592;topicseen#new
in Deutsch   translation available

For a very deep howto on fdupes   especially if you are trying to automate deletions on 3 or more folders
https://krausens-online.de/fdupes-duplikate-finden/

translated      to english via google    https://translate.googleusercontent.com/translate_c?depth=1&hl=en&pto=aue&rurl=translate.google.com&sp=nmt4&tl=en&u=https://krausens-online.de/fdupes-duplikate-finden/&usg=ALkJrhi9yfoptnHQlNP8vfa5iFlktJEoXA

The advantages of hard links

A deletion without a query takes place with the parameter -N. When this parameter -Nis used, the first hit is always received and all other files are deleted.
ATTENTION: The first file that is fdupesaccepted is not always the file that you want to receive.

The use of the parameter is much "safer" -L(creates hard links instead of deleting them).
This parameter is, for example: in fdupes 1.50-PR2.
#> fdupes ./ -rL

• ./anderer_ort/File2-Kopie1.txt
  [h] ./File2-Kopie1.txt
  [h] ./File2.txt
  
  
• ./File1-Kopie2.txt
  [h] ./anderer_ort/File1-Kopie2.txt
  [h] ./anderer_ort/File1-Kopie1.txt
  [h] ./File1.txt
  [h] ./File1-Kopie1.txt
  1
  2
  3
  4
  5
  6
  7
  8
  9
  10
     
  #> fdupes ./ -rL
  
• ./anderer_ort/File2-Kopie1.txt
  [h] ./File2-Kopie1.txt
  [h] ./File2.txt
  
  
• ./File1-Kopie2.txt
  [h] ./anderer_ort/File1-Kopie2.txt
  [h] ./anderer_ort/File1-Kopie1.txt
  [h] ./File1.txt
  [h] ./File1-Kopie1.txt
  
  The "[L]" indicates that the file has now been linked by hard links. As a result, the file is still available in all directories, but only takes up the storage space once.
  You can see this from the inodes of the files.

Yes, I probably should have quoted the original in Deutsch/German 

Which leads to JDUPES

https://github.com/jbruchon/jdupes

jdupes is a program for identifying and taking actions upon duplicate files.

A WORD OF WARNING: jdupes IS NOT a drop-in compatible replacement for fdupes! Do not blindly replace fdupes with jdupes in scripts and expect everything to work the same way. Option availability and meanings differ between the two programs. For example, the -I switch in jdupes means "isolate" and blocks intra-argument matching, while in fdupes it means "immediately delete files during scanning without prompting the user."

Why use jdupes instead of the original fdupes or other duplicate finders?

The biggest reason is raw speed. In testing on various data sets, jdupes is over 7 times faster than fdupes-1.51 on average.

jdupes provides a native Windows port. Most duplicate scanners built on Linux and other UNIX-like systems do not compile for Windows out-of-the-box and even if they do, they don't support Unicode and other Windows-specific quirks and features.

jdupes is generally stable. All releases of jdupes are compared against a known working reference versions of fdupes or jdupes to be certain that output does not change. You get the benefits of an aggressive development process without putting your data at increased risk.

Code in jdupes is written with data loss avoidance as the highest priority. If a choice must be made between being aggressive or careful, the careful way is always chosen.

Looking at the Debian pages for fdupes, and going to the git page Debian uses for fdupes

https://github.com/adrianlopezroche/fdupes

One can see that fdupes is still being maintained.    More confirmation of that is found at https://metadata.ftp-master.debian.org/changelogs//main/f/fdupes/fdupes_2.1.1-1_changelog

So; the choice is yours -  fdupes versus jdupes.   If I was a younger person I would go with jdupes - but since I always use a confirm, I will probably continue to use fdupes.

peace out