- cross-posted to:
- mildlyinfuriating@lemmy.world
- cross-posted to:
- mildlyinfuriating@lemmy.world
cross-posted from: https://quokk.au/c/mildlyinfuriating/p/990534/why
How hard is it to implement email verification?
cross-posted from: https://quokk.au/c/mildlyinfuriating/p/990534/why
How hard is it to implement email verification?
That is also a concern and why I always default to a separate account even for those things, but I wouldn’t assume that data doesn’t get sold to Google regardless.
Google knows when you use their services to sign in, and for what third party they’re authorizing the requests. The data doesn’t need to be sold back to Google.
I’m talking about when you don’t use Google to login.
I prefer to use different email aliases for everything to mitigate that
from what i’ve read, ALL email ( possible 0.000something tolerance/error ) goes through google’s mail-transfer-agents.
If they want a copy of every email that goes across the internet, they’ve got the saturation-of-core-servers to have that.
There simply isn’t any way to bypass that.
on an irrelated note, i wish public key encryption had been normalized, & worked right…
( Snowden got stung by a misconfiguration, 1 time, & if geeks get stung, then it isn’t ready for normals )
🙏
The important part is whether they can associate two identities together. If you use a shared Google login for everything you’re doing their work for them.