I'm not so surprised, given that you cannot write support tickets if the bug prevents you from registering...
Also, I don't think people have high hopes that a broken government website will ever get fixed.
From Wikipedia, I get to https://web.archive.org/web/20010204033600/http://publib.bou...
That has one live link: https://web.archive.org/web/20010107084700/http://publib.bou..., but from there, the trail runs dead.
Do you have a link?
PDF link in the box on the right.
It seems this should just be a single input field styled appropriately, but it feels like there must be an underlying reason I'm missing.
- Six boxes communicate “== six digits, != password” (try to imagine the least tech-savvy user)
- Some people might not be able to quickly hold six digits in their head at once (especially seems to be the case with older people, from my experience), so seeing “I’ve already got two/three/four” visually is potentially an efficiency boost. This also correlates (again, just from my anecdotal experience) with the population that doesn’t have a password manager handling 2FA for them automatically…
- This is probably down to preference, but IMO it also feels faster somehow than a single input field with six digits, when it works properly (with the caveat that it feels much worse/slower if it doesn’t work)
- Now that everyone does it, you’re kinda forced to adopt it as well for recognizability.
But it’s an interesting question – we can’t ever imagine entering postal ZIP codes like that and yet that’s an area where it’d actually make more sense since there’s usually some notion of “more significant” digits at the start vs. end, so you could perhaps do some cool tricks with regard to pre-filtering state, city etc. names. Whereas OTP codes are (AFAIK) essentially fully random digits with no meaningful distinction.
Anecdotally, this seems to be the case on the majority of websites where I have to use such 2FA codes.
Very nice blog layout btw.
(saving you a click: AZERTY has digits on the shift key, and for some reason the JS is handling raw keys rather than processed characters)
Crazy to add complexity like this.
This is just a classic case of a developer situated firmly at the first peak of the Dunning Kruger graph.