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.
Discussion
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.
No. Nip 65 is the future. Kind 3 must be burned and forgotten.
Cool I’ll add the ability to publish NIP 65 lists on https://relay.guide