Event JSON
{
"id": "d908b2d65500f5771f9f354bc02266cec8a0bd576beba4c4d9c66fa7df7a8850",
"pubkey": "fd9067c61394dd227465264c8a67510d6931ca3916b4b98ded0cc4ffc51922ac",
"created_at": 1708881544,
"kind": 1,
"tags": [
[
"p",
"1efe3b1d672caea6329e967c6c08559ce90bdbbdd6f420009755e4ba7485d959",
"wss://relay.mostr.pub"
],
[
"p",
"4421e6f8f57df36e663f1a4568344196e61ea62eb94203c9c02d83bcb3eb9c66",
"wss://relay.mostr.pub"
],
[
"e",
"688b32664981bd1ca8c7a73383fc1934568a82e49cd0014afad43f43d0cca3a5",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.treehouse.systems/users/hugo/statuses/111993260918614044",
"activitypub"
]
],
"content": "nostr:npub1rmlrk8t89jh2vv57je7xczz4nn5shkaa6m6zqqyh2hjt5ay9m9vs9xxa6t this seems to be geared to optimizing for display and human parsing, whereas isn't JSON explicitly intended as a serialization format for machine parsing? Isn't this all better addressed by using one of the myriad JSON display \u0026 parsing tools, e.g. https://fx.wtf/ ?",
"sig": "d25a751544557e79f82d0ec9b133830f65e707d854ae1f125696d0307796840ebc20ec0d110f7b7f8059bea3ab82a1dfe29694e68f76baeb5150bf375c3ae96d"
}
