Two users became one, or one became two
Identity decided by string equality. Nothing raises when it gets the answer wrong — you just get a duplicate account, or a destructive merge.
Curated by Code Recycle Editorial
- 1
Two strings a human would call the same produce different keys, so one person quietly becomes two accounts. No error is raised at any point.
Why it's here: Two strings a human would call the same produce different keys. One person, two accounts.
- 2
Is this the same person again? Exact-match on email catches nobody who is trying.
Why it's here: Exact-match on email catches nobody who is actually trying.
- 3
A fuzzy match scores "123 Main St E" and "123 Main St W" as near-identical -- one character apart, and two different streets half a mile apart. The merge is destructive: the losing record's data is gone.
Why it's here: "123 Main St E" and "123 Main St W" score as near-identical. The merge is destructive.
- 4
The same concert from four ticket APIs, resolved into one event — without merging the tribute band into the headliner.
Why it's here: Four ticket APIs, one event — without merging the tribute band into the headliner.
- 5
Your crawler re-fetches the same page once per utm_source. The duplicate filter reports nothing, because it never saw a duplicate -- the fingerprints genuinely differ.
Why it's here: Your crawler re-fetches the same page once per utm_source, and sees no duplicate.