Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try !politicaldiscussion@lemmy.world
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I create unique email addresses for every organisation and service I deal with, including an obfuscated date, so when an address is compromised I can nuke it with a hard rejection, and regenerate as needed. This all feeds into a catchall mailbox, with server-side sieve rules to filter the stuff I actually care about.
I besides some account specific and burnt addresses, I don’t actively track of any of the addresses I’ve created, it would be in the hundreds by now.
One benefit of this crazy setup is there’s one less common identifier to match across disparate data stores.
Finally, no one should do any of The above. From experience I consider it pathological.
i started to create separate email aliases for every newsletter, account and contact like >10years ago. i still have some few aliases that i shared with friends so these are spread more wide. some of these aliases turned out to be useful as in the platform i created it for lost my data, i got some phishing mail and told the platform admins about their data loss, i then just stopped spam by changing that one single email alias. that happened i think four times.
this year i wanted to get rid of old domains and had to go through all of the aliases there, which turned out to be >400, that was a lot of work, but my setup turned out to be quite a good documentation about what accounts i've set up during that period. some accounts were for platforms that do not exist any more, many for platforms that changed owner (mostly without notice) while some accounts turned out to be stuck like i cannot even delete them, because if i try, that platform freezes the account for "weird looking actions" looks like they just do not want to follow the laws.
overall i think of maybe improving usability by platforms, (free)email providers and also newsletter senders, then creating some specs and try writing RFC style definitions and write a proof-of-concept to make "handshake" and email addresschanges possible and easy for endusers in large scale while achieving the same level of filterless spam protection that i have now.
when i find the time to do it.