Replying to Avatar Vitor Pamplona

All clients always check. However, if the client cannot find your relay list on the biggest relays out there, every client will revert back to a default list. This happens when people reduce their relays to just a few uncommon ones.

To avoid this, it's a good practice to always update your relay lists in all possible relays, not only to the ones you use.
Avatar
Greg 2y ago

Nice and that relay list should be published following NIP 65? (Relay list metadata)

Reply to this note

Please Login to reply.

Discussion

Avatar
Vitor Pamplona 2y ago

Most clients keep the list on kind 3, in the .content field, which hasn't been documented very well. The difference between kind 3 and nip65 is that kind 3 contains not only the relays that you want to use but also a sum of relays from your contacts. It's a fixed list the user controls. Nip65 will only include the list you want to use for yourself. So, it should be a much smaller list.

Avatar
Greg 2y ago

Do you think the “right” solution is using what’s in kind 3 events? It seems like it gives a longer and more useful list.

But NIP 65 is more purpose built to solve this issue.

I can imagine it going either way.

If kind 3 is the right place for this info then I’ll submit a PR for NIP 2 to update it since it explicitly says to ignore the content field.

Avatar
Vitor Pamplona 2y ago

No. Nip 65 is the future. Kind 3 must be burned and forgotten.

Avatar
Greg 2y ago

Cool I’ll add the ability to publish NIP 65 lists on https://relay.guide