Nip65 is not used by almost any client. It's a different approach that doesn't use a fixed relay list to download messages from your friends. It calculates relays on the fly based on your friends NIP 65 or kind 3 events. That's the way moving forward, but we have been slow to adopt. Amethyst just recently started to implement it.
Not sure, I thought it was, but maybe some of the wallet Devs can elaborate?
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ?
Discussion
Gotcha. So a client still has to know a relay which you are likely to have published the NIP 65 event so they’re still going to check a bunch of high usage relays to look for a NIP 65 list or mentions of you to find a relay that’s likely to have it?