Did you know <q> and <blockquote> have a cite attribute? Well, it's worthless. Because why would I use the cite attribute in a quote when it doesn't show up in the user agent? Cluttering my code and increasing file sizes for nothing? No thanks! I put the attribution in the <blockquote> as a link. I know the spec says it's wrong but I don't care. I do it out of spite.
What experts say: use <q> to quote someone, it's more "semantic" and the quotation marks show in the user's language.
Reality: authors only use <q> because they don't know how to type curly quotes in their own language. In fact, why would ANYONE want the quotation marks to change according to the user-agent's language? The rest of the text is still in the original language!
I don't understand why every website requires #2FA now. SMS? You can lose your phone number. #TOTP? Lose device. One time password? Lose where you wrote it. You always need 2 methods in case you lose one, but if a tornado hit your house, you could lose your phone and one-time passwords at once. And if every site asks for it, imagine how many codes you need to keep track of! Why not just send an OTP to your #email, and then make email more secure and recoverable?
Another day of trying to figure out how many #email accounts I should have. It's literally a #security vs. convenience problem. If I keep an e-mail that I don't use for anything but critical authentication and services, I'll never check it, so I'll never know when a critical e-mail comes in. The e-mails I want to be notified about the most are exactly the ones that I don't want to expose access to, so even using an e-mail client feels like a vulnerability. Is it meant to be this hard?