Event JSON
{
"id": "a3ec2acd81f79083fa622d11ff358d9ddd89090b42a54afd1b6bccb1980eeec2",
"pubkey": "8e3ac11e1cfbd1959ffff89d016fd2a6c159c4880cf4fe0274ac3852e21f2b88",
"created_at": 1698186603,
"kind": 1,
"tags": [
[
"p",
"3c745deb3224937af97787803fb018e1e4c208d3e1206f2b01620b49258b2fdf",
"wss://relay.mostr.pub"
],
[
"p",
"4b06a99655066ca3e1a19ecc4bd5c5fd5d0f106a319a8cfb3c414bdff9e17c27",
"wss://relay.mostr.pub"
],
[
"e",
"0a2e81c388a2ffbfa5c6424ebb6e50b9c3a6aa7625f665c7d9ba23e7b8f0fb18",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/varx/statuses/111292357263978160",
"activitypub"
]
],
"content": "nostr:npub18369m6ejyjfh47ths7qrlvqcu8jvyzxnuysx72cpvg95jfvt9l0s5z8jp6 I feel like with binary protocols, there's a marginally higher chance that protocol implementers will follow the spec carefully—a bit of an incidental gatekeeping effect.\n\nThere's a JSON canonicalization spec, but what you really need is a spec for *parsing* JSON safely. One approach would be to parse it, then recanonicalize it according to https://www.rfc-editor.org/rfc/rfc8785 and finally check if it is byte-for-byte identical with the input. But that spec doesn't actually say to do so, as far as I can tell!",
"sig": "2c56cb4afa6a8d1647ff1946dda386d3e60a019eb9b498685a883d448236ef0e49cd3ba27b03cb320eb87d307e0cfd2ab8ec4fb2b3ea19c02fb2186ca4261610"
}