wss://relay.damus.io appears to be still dead and alive at the same time.
I think that manual maintenance of relay lists could be improved with some automation: a relay admin could sign and broadcast a notice that their relay domain (or IP, if the certificate is issued for IP) is outdated and they now recommend some other relay URIs instead (compatible with particular relay lists), so clients could read a notice and suggest replacements (ranked by latency measurements).
Or if admin has nothing to recommend, clients could suggest relay replacements based on NIP-66.
#devstr #nostr
codonaft
npub1al…7rg94
2026-08-28 12:44:27 UTC
Author Public Key
npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94Seen on
wss://nos.lolPublished at
2026-08-28 12:44:27 UTCEvent JSON
{
"id": "00000ba930eb36e5d9c2f5bdd8d9cdf97d0a790b9faef9ac45963792ff6c7197",
"pubkey": "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19",
"created_at": 1787921067,
"kind": 1,
"tags": [
[
"L",
"ISO-639-1"
],
[
"l",
"en",
"ISO-639-1"
],
[
"t",
"devstr"
],
[
"t",
"nostr"
],
[
"nonce",
"272258",
"18"
]
],
"content": "wss://relay.damus.io appears to be still dead and alive at the same time.\n\nI think that manual maintenance of relay lists could be improved with some automation: a relay admin could sign and broadcast a notice that their relay domain (or IP, if the certificate is issued for IP) is outdated and they now recommend some other relay URIs instead (compatible with particular relay lists), so clients could read a notice and suggest replacements (ranked by latency measurements).\n\nOr if admin has nothing to recommend, clients could suggest relay replacements based on NIP-66.\n\n#devstr #nostr\n",
"sig": "4a914932751b87923dc1c91bfe734ff0fd2a0fa732ebf6e8740a098a77c1cfcfa46e6958655b35f8c766dc626941e6743966b3d892ff5dbae3fa996da2477e27"
}