They're conflating a lot of things that don't need to be conflated. You can generate a password for the user locally, when they create an account. You should s

They're conflating a lot of things that don't need to be conflated. You can generate a password for the user locally, when they create an account. You should still be hashing that password, not storing it in plain text. You should still give the user an automated option to generate a new password. You can still avoid sending the password over email, since that's almost guaranteed to be sent unencrypted over an open wire at some point. The beauty of this Twitter thread is that it starts out with an idea that makes some very mild sense, and then immediately descends into madness for no reason. I absolutely love that they consider a password personally identifying information, but are fine collecting emails because, "the user could use an anonymous one if they wanted to."