4 ms·
I don't see the utility of this compared to simply showing 'passwords are identical / not yet identical' live. Perhaps I'm missing something. OK, so a user mak
by nailer 17y ago
I don't see the utility of this compared to simply showing 'passwords are identical / not yet identical' live. Perhaps I'm missing something.
OK, so a user makes a mistake, and they notice their n characters in the first field and their n characters in the second field generate different colors.
How does this help them determine which of the two fields has what they intended to enter?
Also since the user types each field at a separate time, how does the character-by-character hashing help? What utility to the user is there from, having typed 'password' into the first field which shows brown and blue, knowing that typing 'p' in the second field made the second field green?
- codyrobbins 17y agoAgreed — I don't understand how this is much help. Furthermore, it was confusing to me until I understood what it was doing, and — when I did — I similarly thought, 'Why isn't it just telling me when the passwords match?' Your average user is going to be completely perplexed by this and have no idea what it's even for. I would argue that this is far less usable for the average user than the old-fashioned implementation of clicking 'Submit', doing a non-AJAX round-trip, and then displaying a message that the passwords don't match.
- Huppie 17y agoThe idea behind this program is probably not to show you when your passwords 'match' but to show you whether your password is correct. E.g. If you see the colors of your password everytime you log in, you will probably learn that your password is correctly typed if you see the colours purple-green-olive. Whenever you spell your password incorrect (and thus see 'blue-pink-black' for instance) you will notice it immediately, without pressing the 'login' button and being presented with a (not so nice) "Invalid username/password" screen.
- jay_kyburz 17y agoYeah, but its such an insignificant problem, why add the complexity of this solution.
- jballanc 17y agoI don't think the point is to see the two fields' colors match. Based on the run of similar posts to HN, this appears to be an attempt to solve the "you shouldn't mask password fields" problem. That is, once you've set your password, you'll have a three color combination that is memorable. That way, the next time you go to log in, you would (hopefully) notice if you had typed your password in wrong because the colors wouldn't be the familiar set of three. (i.e. You wouldn't be attempting to edit the password field, just clear it and re-enter.)
- extension 17y agoI presume that the intended purpose of this is to give better feedback for a password challenge. I'm not sure why there is a confirm field in the demo. Perhaps to show that the color is consistent. It helps in that it lets the user know that the password is wrong the instant they've finished typing it, which might be a nice touch if it takes a long time to verify a password. They still don't know where the mistake is though, so they have to retype the entire password.
- calambrac 17y agoSo the big win of this feature is that users might get their color combo burned into their head, and submit fewer bad passwords to the server when they bother to manually enter their password and take the time to look at and process the given colors. Wow. Is there a Nobel Prize for web design yet?