Improving the new duplicate detection tool [8.10.18 +onward]

1P_Dave , I wish I knew what was different. The duplicates usually seem identical to me. My assumption that the metadata must differ stems from what tech support suggested in the past. In other words, since the duplicate detector didn't flag it, the metadata MUST be different. (This was back when we had the duplicate detector in OP7, before its removal during the transition to OP8.)

I repeatedly asked about the specific differences, or at least to have them described in general terms. I never received a direct response, only comments about the database format being proprietary, promises to pass it along to the development team, and vague hopes that it might be fixed in a future release. I never got the impression that the issue was thoroughly investigated or that there was much concern about it.

The origin of the issue was my early adoption of moving standalone databases to the cloud in OP6. I had standalone databases on various devices, similar, but none containing the latest version of every password. I assumed there would be a merge function or something to prevent duplicates, but there wasn't. Nor was there any warning against what I did, nor any way to undo it. (After my report, a safeguard to prevent this was added to the code, but it was too late for me and a few others.) My initial databases of about 2000 passwords ballooned to 8000. I've been trying to fix this for, what, over 10 years now?