Event JSON
{
"id": "a55afccfe0c1fdf9197cf6d6494f393a7c5b8f7d89132913883e13ef761cbeeb",
"pubkey": "5ab0ff62d0dc33bfa5c3380d991e650e4c28b949f6d524e2ef77068e8ebf37d5",
"created_at": 1706866934,
"kind": 1,
"tags": [
[
"p",
"9fece4ec0fe7c670707bc5be4293f83f9b97302f1301a16228275494681e5eb9",
"wss://relay.mostr.pub"
],
[
"p",
"4f985166f0a1a734aec150d6320effa53d1ae6dffec621945a0e37359be0a91c",
"wss://relay.mostr.pub"
],
[
"e",
"3a312f392ebc9702545b5d0b5348bf48ec9934b3d2ae0e0cfbd164547e04b644",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://nixos.paris/users/raito/statuses/111861231390548795",
"activitypub"
]
],
"content": "nostr:npub1nlkwfmq0ulr8qurmckly9ylc87dewvp0zvq6zc3gya2fg6q7t6usd5230r Bad implementation bits and core issues with the protocol goes hand in hand together for a large class of issues that I saw so far. It's hard to blame implementations, when the protocol is this vague, seems to have fell in a trap with the JSON envelopes and schemes.",
"sig": "fd09fb37fc2fba5301c08566e4cc956648a0d8788faaf57d93894a07c5c527cebc10b1ad7d19b2aec39826bb22926f86149fbc8d123e9089173161f17a891d31"
}
