Screw that nonsense...
That is unacceptable as well. The current system of username/password needs improvement, NOT replacement.
Requiring users to create longer & more secure passwords that are then salted and encrypted clientside before transmission is the correct solution.
Properly crafted longer passphrase passwords are easy to remember, are impossible to guess and extremely difficult to brute force.
Example(please note, this is not my personal password, if you try using it to access my account W1zzard will likely ban your IP, only warning):
Long.Pass=Phra53s-Canb3fUn
The above passphrase password example is easy to memorize, easy to type out and is unbreakable. This 26 character passphrase meets all of the requirements for proper password security. It is greater than 24 characters, is made up of upper and lower case letters, contains several numbers and special characters making brute-force prohibitively tedious and a dictionary(technical or traditional) type attack would fail as it is acceptably complex. Coupled with the above mentioned proper salting & encryption and passwords like this are unbreakable in the wild. Mixed language passphrase passwords are even more secure.
Example:
Long.Pass=Phra53s-Canb3fUn,paTok
In this case, the same password is mixed with a misspelled insult from a fictional language. Still easy to memorize but impossible to guess or brute-force. With properly implemented 128bit encryption, the fastest computer array currently on Earth would need approximately 1.2billion years to crack it by brute-force methods. Using 160bit encryption that time increases to 43billion years. Even the slowest phone on Earth can handle 160bit encryption without much effort.
These large corporations are overlooking the obvious and need to leave security concerns to security experts instead of nitwits trying to climb the ladder.
Sorry man, IPV6 is ridiculously insecure. "House of Cards" kind of insecure.
Absolutely nothing and it happens all the time.