4 ms·
A year or so ago this was also the case with Facebook [0]. I believe it's a simple compromise between user experience and security. You can probably eliminate a
by baddox 15y ago
A year or so ago this was also the case with Facebook [0]. I believe it's a simple compromise between user experience and security. You can probably eliminate a large portion of user frustration this way. Before you instinctively respond with something like "but security should be the NUMBER ONE priority," realize that you're always making a compromise between user experience and security, and in fact, the two aren't even orthogonal. You could require users to purchase and use biometric scanners to authenticate, but that would likely be very frustrating. Or, you could require users to use a 50 character password with tons of entropy, but that would probably just lead to users leaving, or (perhaps worse) writing their password on a note stuck to their monitor.
[0] http://www.zdnet.com/blog/facebook/facebook-passwords-are-not-case-sensitive-update/3612 http://www.zdnet.com/blog/facebook/facebook-passwords-are-no... —Actually, Facebook wasn't completely case insensitive. It only accepts the chosen password and a version with every character's case inverted.
- sturmeh 15y agoThey gave a pretty good reason for that, case inversion occurs naturally if you have capslock on. It doesn't make the password any less secure. (It's actually only one other password.) They also allow you to change the first letter to caps, which accounts for phones that capitalise the first letter of every sentence you type.
- baddox 15y ago> It doesn't make the password any less secure. (It's actually only one other password.) It does make your password less secure, it's just that Facebook judged it an acceptable compromise between user experience and security.