Event JSON
{
"id": "d53238cbe60481bd22a95962d1334b2cc4953652dc444e350dac04fcba1089d8",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1675380632,
"kind": 1,
"tags": [
[
"e",
"465152e1161a5a81a1e7de4889a783f70c868b33e7e6aa45c6a70c0cf96f194c",
"wss://nostr-pub.wellorder.net",
"root"
],
[
"e",
"0e8345f2ea1c8f705962e29c8770050eb3a25d19143757d26ffa27632a975b91",
"wss://nostr-pub.wellorder.net"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"wss://nostr-relay.untethr.me"
],
[
"e",
"2b83a5058f689e43fabe8b0caacb4acb33ebabd283e9d78fe2c6331411cda94e",
"wss://nostr-relay.untethr.me",
"reply"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"wss://nostr.zebedee.cloud"
]
],
"content": "Ok, I started writing a blog post to fully explain, and I think my scheme might be flawed due to references always pointing to the content's original relay. This might have worked with Blazepoint, since I had a more sophisticated querying mechanism, but I think it won't work with relays as they are, and an indexer of some kind will be necessary, along with lots of special purpose relays that can pick up the slack from personal relays when content goes viral. Anyway, I did draw the picture: https://nostr.build/i/nostr.build_5b647c9ad189229a0cee9b2385cf6db279c39d2135e5204e9afcde91e7bf524f.png",
"sig": "89f80332229eafe4f666a4b504baa12fc172e02c18ef0919e16b7c6bd8da2c69fa2bb1200db20791d7c95d104dbed40151b8af7ce60ececc55b09e01cfd201fc"
}