Event JSON
{
"id": "c21606fce20bf9bd7a1fd511f504fca96d394d31de38ea2ae87e783e0046206b",
"pubkey": "e6a9a4f853e4b1d426eb44d0c5db09fdc415ce513e664118f46f5ffbea304cbc",
"created_at": 1725984300,
"kind": 1,
"tags": [
[
"e",
"ffe90f813efdc7e122a48717f98bf7a312c71e8b34c5468831f4218fc462a8de",
"wss://junxingwang.org",
"root"
],
[
"e",
"d5d40c1e8d37b46084f12fbcfb828fd67ecb461009834465aac57dbd64243058",
"",
"reply"
],
[
"p",
"3c906042e889f081619588980bcf1ebca6a5443022ad6dd8205aba269577212b"
],
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
],
[
"p",
"50de492cfe5472450df1a0176fdf6d915e97cb5d9f8d3eccef7d25ff0a8871de"
],
[
"r",
"https://github.com/nostr-protocol/nips/blob/master/65.md"
]
],
"content": "Oh yeah… I thought you meant relay admin as well.\n\nBut as long as we’re talking about clients, I would love to have a client that could read/write from public and private relays within that same interface.\n\nI was going to say it doesn’t even need to store private relays in the kind 3 relay-url field(s) - then just discovered nip-65 is attempting to supplant this with replaceable events\n\nhttps://github.com/nostr-protocol/nips/blob/master/65.md",
"sig": "3d833d4248d600ada7c6e1f587fe8d3e17a5c55d8a03470cdfd36f1ddae21041bc4c3f1cf09ec6c0f8e068bd11830bad1989b2123ecf63a429506e39e7444ffc"
}