You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was reviewing gnostr-get-relays and noticed gnostr is using the nostr.watch REST API.
Strongly recommend transitioning to NIP-66 for relay liveness determination, as the API is not maintained, has a smaller dataset, and will have an even lesser dataset moving forward (as relays on onion, i2p, and other alternative protocols begin to be monitored). I haven't posted a sunset notice for it, but feel confident it will be Sunset within in the next 12 months.
Was reviewing
gnostr-get-relays
and noticedgnostr
is using the nostr.watch REST API.Strongly recommend transitioning to NIP-66 for relay liveness determination, as the API is not maintained, has a smaller dataset, and will have an even lesser dataset moving forward (as relays on onion, i2p, and other alternative protocols begin to be monitored). I haven't posted a sunset notice for it, but feel confident it will be Sunset within in the next 12 months.
NIP-66: nostr-protocol/nips#230
NIP example implementations:
The text was updated successfully, but these errors were encountered: