Event JSON
{
"id": "ac8e3b5aba232877b63d48e38dcdb187056b982191a633d979915bf39e37df41",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1747413543,
"kind": 1,
"tags": [
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
"wss://nostr.wine/",
"Dikaios1517"
],
[
"p",
"8aa70f4433129dadb71330ac89f62b534caa200a9f3ee349a0f4a5593073d1a6",
"wss://ae.purplerelay.com/",
"snax"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"wss://vitor.nostr1.com/",
"Vitor Pamplona"
],
[
"p",
"472f440f29ef996e92a186b8d320ff180c855903882e59d50de1b8bd5669301e",
"wss://relay.snort.social/",
"MartyBent"
],
[
"p",
"9be0be0e64d38a29a9cec9a5c8ef5d873c2bfa5362a4b558da5ff69bc3cbb81e",
"wss://fabian.nostr1.com/",
"Fabian"
],
[
"e",
"3514e148a245e182c3a5ec453922d211cfef0b2e45777fa0c9fc24115633a441",
"wss://relay.damus.io/",
"root"
],
[
"e",
"47f6a85aab199b64c46d152c6b83f112fcff5ebb98a583e760f5199f5287b4c4",
"wss://wot.brightbolt.net/",
"mention"
],
[
"e",
"63db5144f102ad80ce28af9029f8740b5309754dd0a039283c2f7fb87f04a975",
"wss://relay.nostrplebs.com/",
"reply",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
],
[
"client",
"Coracle",
"31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690"
]
],
"content": "That would be ideal, but it's probably more of a job for clients helping users pick their relays. I've wanted to build a relay management client for a long time that checks relay availability, specs, policy, etc (directly and via nip 66), as well as probing the relay for user access. Then, warning the user if a relay goes down or misbehaves, and migrating notes back and forth when selections change. Clients shouldn't duct-tape the network together with broken heuristics if users can't be bothered to make good relay selections.",
"sig": "f303c594c5ecfe2674b00d62eb40397200e1219ba7433f323726b9533a0f143d59ba553019935d08363074bbdf8b714c29b70ad208e7d001a136cc23e53de284"
}
