Can we have a relay type flag on NIP-11 so client devs can block people from putting these relays on their inboxes/outboxes? your issue https://github.com/nostr-protocol/nips/issues/1282 already perfectly describe it
Discussion
That could be done but what if some relay doesn't use the flag? And what if a client doesn't respect the flag?
Ultimately other clients will have to work around this anyway.
There are tons of other issues that could arise from kind:10002 relay lists:
- the relay may be offline
- the URL may be invalid
- the relay may have banned the user
- the list may be outdated and the relays where the list is being fetched may have banned the user and continued to serve old outdated
That's why I think any Nostr app above some threshold of complexity must eventually implement a scheme like seen in https://how-nostr-works.pages.dev/#/pathological, relying on relay hints from others and decreasing scores for relays as they're perceived to not return new notes from the target users, so new relays get tried until some succeed or until a new better relay list is found.
By the way, this scheme is heavily inspired by an old version of https://github.com/mikedilger/gossip (the new version is similar too, I think) and is implemented in https://gitworkshop.dev/fiatjaf.com/nostrlib/tree/master/sdk/hints/keys.go and used in njump and nak and some other minuscule things. It's also partially implemented in https://jsr.io/@nostr/gadgets/doc/hints but not used anywhere as far as I know.
I understand the other relay list issues, but having a flag on NIP-11 is a very easy gain to block users from adding relays like purplepag.es or algo.utxo.one to their relay lists (I have seen multiple times), and also display a warning to the user if they have those relays there and explain to the user the relay type