Replies (4)
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.
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.
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.
