3 ms·
I am with you on that. I am so surprised how fragile systems are. 1. I use email like firstname@lastname.email How many times I end up seeing that my email wou
by outcoldman 3y ago
I am with you on that. I am so surprised how fragile systems are.
1. I use email like firstname@lastname.email How many times I end up seeing that my email would be in the system like fistname@lastname.email.gmail.com or other variations. And how many services just do not accept .email.
2. Idea of using unique emails like domain@firstname.lastname.email broke so many things. Like integration between services (moviesanywhere). Services merging (mint and turbotax). But overall idea worked to see how unsecure my data was at various services like paybyphone (some parking app in seattle) or even linkedin. How much spam I get on those specific emails.
And yes. Signing in via oauth provides is terrifying. Just only see more issues with that.
- gregmac 3y ago> broke so many things I've been doing it for about 20 years, and I can't even recall anything being broken or not working, but maybe I'm not using services that connect like that. The most annoying thing I can think of is when I sign up using "example.com@my.domain" and it tells me "example.com" isn't allowed in the email address... but this is rare, and easily worked-around. On the other hand I know several services that were either compromised or sold their email list. Back when email filtering was mediocre at best, it was easy to make rules to completely filter those addresses out.