101 reputation
2
bio website
location
age
visits member for 2 years, 9 months
seen Mar 12 at 19:01

Jan
29
comment Should users be allowed to use any special character they want when creating a password?
@supercat In that incredibly unlikely scenario, they would simply rest their password, the same as if they had forgotten it.
Jan
28
comment Should users be allowed to use any special character they want when creating a password?
@supercat No, your implementation of the normalization algorithm would have to be updated from time to time as new code points are allocated for diacritics, but 1) that's going to be pretty uncommon going forward, as Unicode already has a very rich set of diacritics, 2) it's all table driven, so you only have to incorporate the new Unicode data, not change logic, and 3) it's probably done by your language runtime, so you get it "for free" when you upgrade.
Jan
28
comment Should users be allowed to use any special character they want when creating a password?
There is a very simple answer to your last question. Simply allow users to use a wide variety of characters, and see whether the number of password reset requests actually goes up by a statistically significant amount. If not, don't borrow trouble.
Jan
28
comment Should users be allowed to use any special character they want when creating a password?
Honestly, NAT? What possible relevance does that have? Telling your Chinese, Arabic, Korean, Russian, Hebrew, Greek, et cetera ad nauseam users that they must use Latin letters in their password is completely unacceptable in the modern age, and is not necessary for security.
Jan
28
comment Should users be allowed to use any special character they want when creating a password?
I think it would be best for us all to just agree to never use any system designed or built by @Blam.
Jan
28
comment Should users be allowed to use any special character they want when creating a password?
Unicode normalization forms are very well specified, so there shouldn't be a problem with diacritics as long as they are normalized before hashing.
Jan
28
awarded  Commentator
Jan
28
comment Should users be allowed to use any special character they want when creating a password?
@Blam Unicode is a 21-bit character set. It has far more than "60 some thousand characters", although most of the 2^21 code points are not allocated, and may never will be.
Dec
12
comment Why do some users complete forms all in capital letters?
@slicedtoad Fair point. I should have said latin-alphabet-centric.
Dec
12
comment Why do some users complete forms all in capital letters?
DOS doesn't have anything to do with the CAPS LOCK key being on permanently.
Dec
12
comment Why do some users complete forms all in capital letters?
This is very Western-centric. I also disagree very strongly with "If your letters/reports look ugly with uppercase names, it's a problem with the letters/reports." Everything looks ugly in ALL CAPS. The solution to getting some capitalization wrong in MacDonald is not to get all capitalization wrong in MacDonald.
Dec
12
comment Why do some users complete forms all in capital letters?
@xeor I don't believe that's true, that upper case letters are easier to distinguish, and in fact I believe I've seen a study that shows the contrary although I don't have a reference at hand.
Apr
30
comment Traffic light, no more shapes?
I think it's a false assumption that different shapes for the lights would have to mean different shapes for the hoods, although it might require rounding off the top corners of the square red light. See another answer to this question for examples with different shapes and symbols in current use.
Feb
7
comment CAPTCHA on mobile: what are the alternatives?
Another CSS property is clip which can hide a field by i.e., clipping it to 1x1 pixels. Another thing to think about is how all these affect visually impaired users. For instance, I believe screen readers will not read a field hidden with display: none but will read a clipped field.
Jan
28
comment Why not use ellipsis to ask the user?
You mean "imperative". "I have a car" is active voice. Passive voice would be something like, "A car is being had..."
Jun
14
comment How do we stop users overpaying in financial web forms?
It isn't even an answer. What you've said is, you'd fix it by fixing it so that it was fixed. Your update improves it slightly. Update it again to remove everything before "UPDATE" and you'll be on the right track.
Jun
14
awarded  Supporter
Jun
14
comment How do we stop users overpaying in financial web forms?
I am absolutely against using multiple fields for input of a single value. It's like the bad old days of three separate fields for the area code, exchange, and station of phone numbers. I'd prefer one of the other solutions. Or flip it around and let them enter in a single field, but show them separate pounds and pence when asking them to confirm.