#humaninputdevices — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #humaninputdevices, aggregated by home.social.
-
The #nosh Guide has a whole chapter going into a lot more detail on HID configuration; which can range at the administrator's discretion from explicitly choosing accept-all-HIDs to a strong stance on supernumerary, misbehaving, or downright malicious #HumanInputDevices.
Given that I was one of several people who proposed going this way in the 1990s, it is long past the time that recompiling one's kernel was the way to choose what #HumanInputDevices to trust.
http://jdebp.info/Softwares/nosh/guide/user-virtual-terminal-configuration.html
-
The #nosh Guide has a whole chapter going into a lot more detail on HID configuration; which can range at the administrator's discretion from explicitly choosing accept-all-HIDs to a strong stance on supernumerary, misbehaving, or downright malicious #HumanInputDevices.
Given that I was one of several people who proposed going this way in the 1990s, it is long past the time that recompiling one's kernel was the way to choose what #HumanInputDevices to trust.
http://jdebp.info/Softwares/nosh/guide/user-virtual-terminal-configuration.html
-
The #nosh Guide has a whole chapter going into a lot more detail on HID configuration; which can range at the administrator's discretion from explicitly choosing accept-all-HIDs to a strong stance on supernumerary, misbehaving, or downright malicious #HumanInputDevices.
Given that I was one of several people who proposed going this way in the 1990s, it is long past the time that recompiling one's kernel was the way to choose what #HumanInputDevices to trust.
http://jdebp.info/Softwares/nosh/guide/user-virtual-terminal-configuration.html
-
My code (because of the way that #USB #HumanInputDevices work) has to store button/key press information as an array of boolean flags in two distinct places (1 local and 1 shared), so of course it has array bounds checks.
The Elecom Deft's report descriptor bug had me looking for quite a time for where I'd accidentally put the wrong bounds check on mouse button values.
-
My code (because of the way that #USB #HumanInputDevices work) has to store button/key press information as an array of boolean flags in two distinct places (1 local and 1 shared), so of course it has array bounds checks.
The Elecom Deft's report descriptor bug had me looking for quite a time for where I'd accidentally put the wrong bounds check on mouse button values.
-
My code (because of the way that #USB #HumanInputDevices work) has to store button/key press information as an array of boolean flags in two distinct places (1 local and 1 shared), so of course it has array bounds checks.
The Elecom Deft's report descriptor bug had me looking for quite a time for where I'd accidentally put the wrong bounds check on mouse button values.
-
I don't really have a wide enough sample set for that conclusion.
The aim of the collection wasn't to cross-check manufacturers; it was to test that my softwares could handle things such as devices that have no NumLock key, the 104/105/106/107/109-key layouts, "office"/"multimedia" keyboards, and devices that report being multiple keyboards and mice at once.
So it's annoying when a keypress/button not registering turns out not to be my bug.
-
I don't really have a wide enough sample set for that conclusion.
The aim of the collection wasn't to cross-check manufacturers; it was to test that my softwares could handle things such as devices that have no NumLock key, the 104/105/106/107/109-key layouts, "office"/"multimedia" keyboards, and devices that report being multiple keyboards and mice at once.
So it's annoying when a keypress/button not registering turns out not to be my bug.
-
I don't really have a wide enough sample set for that conclusion.
The aim of the collection wasn't to cross-check manufacturers; it was to test that my softwares could handle things such as devices that have no NumLock key, the 104/105/106/107/109-key layouts, "office"/"multimedia" keyboards, and devices that report being multiple keyboards and mice at once.
So it's annoying when a keypress/button not registering turns out not to be my bug.
-
I don't really have a wide enough sample set for that conclusion.
The aim of the collection wasn't to cross-check manufacturers; it was to test that my softwares could handle things such as devices that have no NumLock key, the 104/105/106/107/109-key layouts, "office"/"multimedia" keyboards, and devices that report being multiple keyboards and mice at once.
So it's annoying when a keypress/button not registering turns out not to be my bug.
-
I don't really have a wide enough sample set for that conclusion.
The aim of the collection wasn't to cross-check manufacturers; it was to test that my softwares could handle things such as devices that have no NumLock key, the 104/105/106/107/109-key layouts, "office"/"multimedia" keyboards, and devices that report being multiple keyboards and mice at once.
So it's annoying when a keypress/button not registering turns out not to be my bug.
-
It's amazing how bug-riddled USB HIDs are. Two of my test devices are significantly broken.
The fancy 8-button Elecom Deft trackball only reports 5 of its buttons as variable inputs. The remaining 3 are mis-designated to be constant bit values.
The Technika multimedia keyboard tells the host that its Music Player key is instead the Consumer Control Configuration key.
Looking around, I don't see people patching these faulty USB report descriptors.
-
It's amazing how bug-riddled USB HIDs are. Two of my test devices are significantly broken.
The fancy 8-button Elecom Deft trackball only reports 5 of its buttons as variable inputs. The remaining 3 are mis-designated to be constant bit values.
The Technika multimedia keyboard tells the host that its Music Player key is instead the Consumer Control Configuration key.
Looking around, I don't see people patching these faulty USB report descriptors.
-
It's amazing how bug-riddled USB HIDs are. Two of my test devices are significantly broken.
The fancy 8-button Elecom Deft trackball only reports 5 of its buttons as variable inputs. The remaining 3 are mis-designated to be constant bit values.
The Technika multimedia keyboard tells the host that its Music Player key is instead the Consumer Control Configuration key.
Looking around, I don't see people patching these faulty USB report descriptors.
-
It's amazing how bug-riddled USB HIDs are. Two of my test devices are significantly broken.
The fancy 8-button Elecom Deft trackball only reports 5 of its buttons as variable inputs. The remaining 3 are mis-designated to be constant bit values.
The Technika multimedia keyboard tells the host that its Music Player key is instead the Lock Session key.
Looking around, I don't see people patching these faulty USB report descriptors.
-
It's amazing how bug-riddled USB HIDs are. Two of my test devices are significantly broken.
The fancy 8-button Elecom Deft trackball only reports 5 of its buttons as variable inputs. The remaining 3 are mis-designated to be constant bit values.
The Technika multimedia keyboard tells the host that its Music Player key is instead the Lock Session key.
Looking around, I don't see people patching these faulty USB report descriptors.