I disagree a bit here. I like passwords and this fad really gets on my nerves. I like to authenticate with a passphrase because easy always wins in computer sci

I disagree a bit here. I like passwords and this fad really gets on my nerves. I like to authenticate with a passphrase because easy always wins in computer science. Ever used extended authentication against MS services where you have to register your app to get a specific API key? Me neither because I stopped interfacing them, the hassle was too much. Passwords aren't that difficult if you have a system which works as a seed to calculate passwords for a service where a leak doesn't allow for conclusions in the other direction. Ok, not that easy, but manageable. You could use a std password and append the name of the service and in most cases that would suffice if your plaintext pwds don't leak. I have no problem with this fad if we keep passwords as a option. I can live with certs, but I also stopped using github already, even if I rarely used the pwd option at all. Microsoft wants me to install their silly app. Already had it once, didn't like it and I don't trust their apps on my phone. I already hate when services profile my machine. I use many of those and at some point I already stopped using services because I didn't want to check my mail again... Security theatre and other ambitions to the largest degree. I have no problem with that if you give me the option. My passwords do work. Those of other people also work in most cases. There are sometimes these service accoutns which use 'batman' as a password. That is bad and lazy but also a solvable problem. I would argue that password policies are bad too, aside mabye from length. Adding any other rule is silly and compromises security and accessibility in my opinion.