Also, I never assume a relay is broken.... just that it isn't working right now. So it never stops trying. But exclusions of 600 seconds are long enough that this doesn't matter much.
Sometime in the past I coded a way for users to delete (knowledge of) relays that they knew were "dead". The code didn't work and after some debugging I realized that it actually did work, but the relay got recreated because data in my local database referred to it, and any reference to a relay URL makes sure a relay record exists for it and starts collecting statistics on it. So it just gets deleted and recreated by the other logic. Even if I deleted the events in the local database, new events on nostr would recreate it. I would have to mark it with a tombstone saying to never recreate it... which seems wrong because the DNS name might one day be used for a relay again.
I also pick relays judiciously. When I need to read from someone's set of outboxes (or inboxes), I choose the relays that are most likely to be working.
The console log shows all kinds of relay errors and complaints. I just ignore most of it.
Mike Dilger ☑️
npub1ac…9p35c
2025-08-22 19:42:29 UTC
in reply to nevent1q…apv9
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35cPublished at
2025-08-22 19:42:29 UTCEvent JSON
{
"id": "8b4fc5fd233b32757fdcf0308988fa982ffc3504d119bbb4158f43d5ad1f283c",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1755891749,
"kind": 1,
"tags": [
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"c6603b0f1ccfec625d9c08b753e4f774eaf7d1cf2769223125b5fd4da728019e"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"e",
"b6b1904757e901607071ce339307de1c8575b58b5c8b7f043b8f41dbdb95b928",
"wss://haven.accioly.social/",
"root",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"e",
"7adc6351a6c8ab1dbc464cff42fff0be279ec35efb2ba474b0ba0f2f40090b49",
"wss://wot.utxo.one/",
"reply",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
]
],
"content": "Also, I never assume a relay is broken.... just that it isn't working right now. So it never stops trying. But exclusions of 600 seconds are long enough that this doesn't matter much.\n\nSometime in the past I coded a way for users to delete (knowledge of) relays that they knew were \"dead\". The code didn't work and after some debugging I realized that it actually did work, but the relay got recreated because data in my local database referred to it, and any reference to a relay URL makes sure a relay record exists for it and starts collecting statistics on it. So it just gets deleted and recreated by the other logic. Even if I deleted the events in the local database, new events on nostr would recreate it. I would have to mark it with a tombstone saying to never recreate it... which seems wrong because the DNS name might one day be used for a relay again.\n\nI also pick relays judiciously. When I need to read from someone's set of outboxes (or inboxes), I choose the relays that are most likely to be working.\n\nThe console log shows all kinds of relay errors and complaints. I just ignore most of it.",
"sig": "3162b7c9e427a1e6dfd0c046e357611fe519fbc50878efc972f8d3a7dd2ce591fc3d62d859a645f2a175e554af465f97fd3a6d1449e990939432249792a2ad01"
}