well, I accidentally made a keyboard backwards.
-
@foone does it listen on loopback because I have a funny idea
-
@munin yes? but it's a pico-w so I can't exactly NC-loop it to itself
-
aw, hell. so no fun "figure out the resonant frequency of the keyboard" then.
-
-
I now have an HTTP proxy for my keyboard. You just hit http://localhost:5000/65 and it'll send the UDP for you, so it types an "A"
-
@whitequark @munin bad idea:
keyboard that lets you reprogram the firmware, and it does it by typing out it's own source into the attached PC
(hard mode: it includes the compiler/programmer binaries)
-
hmm. I might make it scancodes instead of ASCII, just because actually programming scancodes properly into the other end of the keyboard is a pain, so maybe I'll just let each key send whatever number it feels like, then I'll make the HTTP proxy translate them. why not?
-
I mean it's terrible but it saves me like 5 minutes of manual work so who is to say if it's bad or not?
-
one of my keyboard keys didn't boot up properly, because while I had the right boot files in the right places, I had left a bootable floppy disk in the drive. no "Z" key for me
-
M [email protected] shared this topic
-
@foone Taking the long way to KVM over IP?
-
@keithmann building a very bad keyboard, so it's 60% insecure protocol converters
-
Solarbird :flag_cascadia:replied to Foone🏳️⚧️ last edited by
@foone stop making me want to make a keyboard that talks Commodore Serial Bus.
-
Foone🏳️⚧️replied to Solarbird :flag_cascadia: last edited by
@moira that's not a bad idea.
-
I gotta figure out how to store some webapp state so I can keep track of if the shift key is down, because that's a separate HTTP request
-
@foone first keyboard to require cookies
-
@astrid thankfully my requesting system doesn't even support cookies (unless I manually track/pass them) so that's out. I'm just making it server-wide state
-
Foone🏳️⚧️replied to Foone🏳️⚧️ last edited by [email protected]
how it works:
$ curl http://localhost:5000/29
unshifted
$ curl http://localhost:5000/6
ok (types "a")
$ curl http://localhost:5000/29
shifted
$ curl http://localhost:5000/6
ok (types "A")(29 is the scancode for "shift", 6 is the scancode for the "a/A" key)
-
-
@retroswim @foone No no no, the button should be held down for as long as the HTTP request body is held open. So you need to do:
$ curl http://localhost:5000/29 -d @- &
$ curl http://localhost:5000/6
$ fg
^D -
@retroswim that's not actually possible, because the keyboard key for "6" is running on a separate virtual computer than the shift key, and they can't communicate with each other!
