- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
…deleting records could cause big problems. Referential integrity across database tables simply wouldn’t allow it… it would cause a resonance cascade.
So, to get around the problem, a lot of places simply “overwrite” records when they are deleting them. They replace certain fields with garbage so the structure of the data remains, but the human elements are no longer present. At the heart of those “certain fields” are email addresses, the most widely used identifiers on all the web. And that, dear reader, is how we got to this cursed discovery.
I saw a discussion on the internet where someone mentioned that they deleted users in their app by overwriting their email addresses with
$somethingRandom.com. Mmm, I thought - I wonder how common of a thought process that is? I bet whoever ownsdeleteduser.comgets loads of emails!I decided to check it out, but to my genuine surprise - no one owned
deleteduser.com, so now I do.Source [web-archive]
I bought a similar domain for setting up wildcard forwarding addresses. Let’s just call it
funnyemail.comI have Simple Login set up so I can create (and destroy) simple throwaway email addresses using
*spam@funnyemail.com, likelemmy.spam@funnyemail.comwhen I need a quick account.What I wasn’t expecting is that a couple of times per year I get something unexpected to
nospam@funnyemail.comorihatespam@funnyemail.com. Most recent one was an e-vite to a child’s birthday party.I’m kinda curious to set up a folder for
*@funnyemail.comjust to see who else is tapping into it for more than just*spamaddresses