Event JSON
{
"id": "ad1c3f818f1844dce50497c6165e2aa976c2185cf5b3e019bdd997cc8559a289",
"pubkey": "dc6381215e656a56d81495cef020a0a291cdcb0195398bdded551ee3938dd9a0",
"created_at": 1718319186,
"kind": 1,
"tags": [
[
"e",
"485316205898ed9d37a99db9e9ebfbe3719fe1b359cff1cac51ae981f3b039c7",
"",
"root"
],
[
"e",
"db3a6e49f1af904fa0a9821528941ede7dd95a822df50e1b598f62c396fc4a54",
"",
"reply"
],
[
"proxy",
"https://aus.social/@jpm/112611766185148778",
"web"
],
[
"p",
"dc6381215e656a56d81495cef020a0a291cdcb0195398bdded551ee3938dd9a0"
],
[
"p",
"04f8915424c713657ad6ce59443d28dbdcf5832687c9af560ae388f59276a137"
],
[
"proxy",
"https://aus.social/users/jpm/statuses/112611766185148778",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://aus.social/users/jpm/statuses/112611766185148778",
"pink.momostr"
]
],
"content": "yep this was pretty much along the lines I was thinking. I’d probably use the high bit of the scan code for key-down/key-up. Would it be worthwhile using all 8 bits of the modifier to distinguish between left/right modifiers same as USB-HID-keyboard does (possibly using the exact same data, make it easier, in exchange for more difficult parsing of key-down/up)?",
"sig": "8e888711d00d1affa557de1dc1bcd62ebc6d3fcb63f124ff5714d5a85770b605200e6d6065db8cf1257525455179491c3d80585fc0e7205ab9dedce68727fe5b"
}