DOOM-3-BFG VS czkawka

The Bethesda representative said that they do not publish which OSS libraries they use but that they comply with any notice requirements. I admit, the claim on my side is somewhat thin, but there is one third party library (Base64.cpp) in DOOM 3 BFG that requires notice and states:

Even idTech 3 used third party components as listed in the description here: https://github.com/id-Software/DOOM-3-BFG. Newer versions of idTech use Vulkan for rendering. For that, they are basically forced to included the header files of Vulkan which are licensed under Apache 2. So it has to be mentioned somewhere.

I guess you can still write valuable software, even more complex than most people can write, with simple (03) C++. Like Doom 3: https://github.com/id-Software/DOOM-3-BFG

> What you are describing

On the other hand, I believe what you are describing is the exact meaning of FUD. In that precise order: "in C++ they have serious consequences" is fear, "There are bugs in the code--probably in your code--right now" is uncertainty, and "Some might be CVEs" is doubt.

According to https://github.com/id-Software/DOOM-3-BFG

Doom 3 was released in 2004. The engine has come to be known as "Id Tech 4", and it's open source. Written mostly in C++, looks like.

Id Tech 4 is currently Open Source (GPL licensed)

I believe doom 3 source is published on github so people can have a look for themselves if they want.

Doom 3 is a perennial favorite for "most beautiful C++ codebase" lists [0]

[0] https://github.com/id-Software/DOOM-3-BFG

https://github.com/qarmin/czkawka by far the best of anything iv tried

I've used Czkawka (https://github.com/qarmin/czkawka) because it does Lanczos-based image duplicate detection, which makes it more practical for me.

Maybe it's a setting you made or the files, not sure. You can try another software czkawka to see if you get better results with it.

For static images i used https://github.com/qarmin/czkawka and it works well enough. I think. But when i used it on a folder with gifs and their jxl conversions, it shows nothing. SURELY this could not be user error, rrrright?

I used to use DupeGuru which has some photo-specific dupe detection where you can fuzzy match image dupes based on content: https://dupeguru.voltaicideas.net/

But I switched over to czkawka, which has a better interface for comparing files, and seems to be a bit faster: https://github.com/qarmin/czkawka

Unfortunately, neither of these are integrated into Photoprism, so you still have to do some file management outside the database before importing.

I also haven't used Photoprism extensively yet (I think it's running on one of my boxes, but I haven't gotten around to setting it up), but I did find that it wasn't really built for file-based libraries. It's a little more heavyweight, but my research shows that Nextcloud Memories might be a better choice for me (it's not the first-party Nextcloud photos app, but another one put together by the community): https://apps.nextcloud.com/apps/memories

Czkawka can do this.

There's always the well-respected tool, Czkawka. Or, of the CLI is your thing, jdupes is a good option.