Catch-all address 😎
Comment on God ****** dammit, here we go again
artyom@piefed.social 1 month agoAnd an email alias.
wreckedcarzz@lemmy.world 1 month ago
artyom@piefed.social 1 month ago
I use either, depending on the application.
Comment on God ****** dammit, here we go again
artyom@piefed.social 1 month agoAnd an email alias.
Catch-all address 😎
I use either, depending on the application.
stealth_cookies@lemmy.ca 1 month ago
I hate how many places don’t allow for + aliases. I want to know who leaked my email.
T156@lemmy.world 1 month ago
At the same time, it is trivially easy to strip a + alias, so I’d not trust it to do anything much at all.
Miaou@jlai.lu 1 month ago
If you use aliases for all services, it makes it slightly harder to automate trying one leaked email on another site, since the hacker needs to add the new alias on the other service.
No one is going through of all these credentials manually, so any extra obscurity can actually bring you security in a pinch. Although if you have different passwords this shouldn’t matter much…
Anivia@feddit.org 1 month ago
No, you just run a simple Regex on both combolists and are done. It literally takes seconds
artyom@piefed.social 1 month ago
No + required. There are hundreds of companies offering aliases using their shared domain.
CodenameDarlen@lemmy.world 1 month ago
Even if your alias is leaked they can remove the + part and it’ll lead to your original email.
Fmstrat@lemmy.world 1 month ago
+aliases are convenience aliases only. They are often stripped from ID datasets. Better to use a real alias.jagermo@feddit.org 1 month ago
I use my own domain with a catchall, works like a charm