Re:The Google plasma globe affair of 2012
by telotortium on Monday October 10, 2022 @06:34PM
(#33157187)
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
[ Parent
| on HN ]
Re:The Google plasma globe affair of 2012
by Scoundreller on Monday October 10, 2022 @09:47PM
(#33158533)
Reminds 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.
Re:The Google plasma globe affair of 2012
by nyanpasu64 on Tuesday October 11, 2022 @01:09AM
(#33159733)
Meanwhile on some UIs, I can click buttons after they're drawn and they do nothing unless you wait for half a second or more.
Re:The Google plasma globe affair of 2012
by Scoundreller on Tuesday October 11, 2022 @04:23PM
(#33168770)
That 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…