Damus still uses a legacy unspecified format (as do/did many clients like Amethyst) where the list of relays is set on the content field of kind 3 follow lists. You cannot specify which ones are used for reads and which ones are used for writes. It’s on my list of things to do to fix for Damus on iOS, as part of my plan to support the outbox model.
I just popped over to Damus, though. It looks like it isn't using this list at all.
nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3g4h5cp7 what relay list is Damus using? It looks like it has only populated the relays from my "General Relays" list in Amethyst, and isn't using kind 10002 at all. What's more, I have no way to set which ones are read and which ones are write. Does Damus treat them all as both read and write?
Discussion
I don’t think so, nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 switched us over to the proper list
Not in the latest version I am running, which looks to be 1.14 (959). It's definitely getting the list from my kind 3.
The kind 3's content field has "read": true, "write": true after each of the relays in the list, so I know that you CAN specify which is read and which is write on the kind 3. It just doesn't look like Damus supports doing so.
This version supports NIP-65 lists, but has a fallback to kind:3 if it cannot find a NIP-65 list.
What makes you say it gets the list from the kind:3? What symptoms are you experiencing? It's possible you are running into some kind of edge case.
Ok. Just published an update to my 10002 and it seems Damus found it. Not sure why it didn't find it before, as I had it blasted all over the place. 😂
It was just my kind 3 relays before that, so it makes sense that it would fall back to those if it can't find the 10002.
Thank you, gents!
nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf this has migrated over to NIP-65, (but without full outbox support). Some relevant new files of this migration would be `UserRelayListManager.swift` and `NIP65.swift`.
We still use the legacy format as a fallback, but give preference to NIP-65 lists.
Oh, that’s news to me. Great!
For the love of God, just make sure to NOT add the kind3 list directly into the NIP-65 lists. This has created so many issues for outbox systems because each relay list becomes MASSIVE.
i was thinking of adding a relay limit when adding relays. I've seen users add like 69 relays
I am adding the kind3 stuff into new lists which I called Proxy and Broadcasting as below. Terrible names, but it separates the information that followers need to know (which should be in NIP-65) from the relays the user wants to use for his own feeds/broadcasting. Separating the two is paramount in my mind.
Mandatory "nice" activated 🤭