3 ms·
Google's actual fix was to install a service that detects if keystrokes are being made too quickly for a human (by default, I believe it's 5 keystrokes per 50 m
by telotortium 4y ago
Google's actual fix was to install a service that detects if keystrokes are being made too quickly for a human (by default, I believe it's 5 keystrokes per 50 milliseconds), and if so, eject the USB device: https://github.com/google/ukip https://github.com/google/ukip
- Scoundreller 4y agoReminds me of when I ran some autohotkey experiments on a citrix-type system. Turned out I could click on controls before they were even drawn on the screen for super-human speed.
- nyanpasu64 4y agoMeanwhile on some UIs, I can click buttons after they're drawn and they do nothing unless you wait for half a second or more.
- Scoundreller 4y agoThat kinda makes sense to ensure users don’t click on something that they didn’t have enough time to interpret. I’ve encountered some interesting situations where clicking and hitting a mouse’s scroll wheel would scroll the point of focus on the next screen…