why? 10002 🤷‍♂️

or are you saying for clients that use relays and don't sync them to 10002?

Reply to this note

Please Login to reply.

Discussion

Yes, many/most are not syncing it. I suspect they only pull that once, at setup.

I hate relay syncing tbh

No. I meant syncing which relays you are suppose to connect to.

yeah, I know, my wording wasn't clear (although I do hate the concept of relays syncing among themselves too 😂)

I don't like the idea of clients syncing which relays to connect to, but I think once we have a relay groups NIP this will be less of a problem

Agree.

Ideally a client should connect to the needed relays depending of the information it wants to get or send, not to a fixed list.

In a social client that will depend on the follows list, and the follows' preferred relays.

The 'gossip model', they call it.

Well, 10002 events are not for storing configuration settings:

"The primary purpose of this relay list is to advertise to others, not for configuring one's client."

https://github.com/nostr-protocol/nips/blob/master/65.md

I reckon storing client settings should be done in a specific "list" (maybe a private list) as defined in NIP-51 (still a PR).

You could use NIP-65 as your client's settings if you wanted them to match what you advertise. Or you might have a reason to use additional relays that you don't advertise to others, and store that information elsewhere, perhaps in a NIP-51.