@raccoon this is a good meme and all, but is terrible cybersecurity practice
as a programmer, i do NOT want to store your password. that is WAY too easy to do slightly wrong in a way that will leave everyone vulnerable if i ever experience a data breach and is definitely something best left to the professionals, like google and github and whatnot. they let you log in through their website, they store your password using their billions of dollars of infrastructure that they use to keep passwords safe that i do not have, and they pass me an auth token, which if it gets leaked in a data breach, is pretty much useless outside of my website. also, if you want to delete your account from my website, you don't even have to go to my website, you can just log into google's OAuth management system and say "i don't want to be associated with this website anymore" and it'll zap the OAuth key and unless i kept your email address i won't be able to interact with you at all anymore.
@AVincentInSpace @raccoon Whilst I understand it's difficult : I don't care, that is the cost of doing coding on the web.
I'm not letting Google or Facebook have custody over my credentials for other sites. It was already bad enough in December 2024 when my Meta account (*only* used for VR) was locked out for 10 days due to an issue at Meta's end. As a result, my VR headset was an unusable brick.
It's already bad enough that Google are almost as evil as Facebook at scraping your data, and they might potentially lock you out because you're in a new location and don't have your mobile with you.
Microsoft? Trust them a bit more, but if Azure goes down that potentially bricks many sites all at once.
Apple? Look at the example of the 30 year Apple user who had their entire digital Apple existence blocked due to a dodgy gift card.
Things like Discord? They already had a personal details breach of age verification information held by a third party, which they said they didn't store.
"but is terrible cybersecurity practice"
That depends on what I'm trying to protect. If I'm trying to protect my account on your specific webpage then it's not ideal, no, but if I'm trying to protect my overalll privacy and identity across the Internet in general, then it's still the best option.
Good point, but storing an automatically-generated one-off password exposes the user very little.
I am glad that I am not alone. And even better I am in so distinguished company.
<username>+<sorting-key>@<DOMAIN>.<TLD> addresses (when I don't feel like logging in to create a new alias or just want to use one of my throwaway webmail-providers as a registration-recipient)