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?
Replies (3)
Tracked it down. Looks like the list of relays Damus uses are found in the user's kind 3 follow list. Specifically under the "content" tag.
Why is Damus using this as the primary source for a user's relay list, instead of kind 10002, and why does the user have no control over which ones are read and which ones are write?
hist.nostr.land as an inbox relay?
There's definitely some interesting choices in your 10002 as well. 😂
What client do you use primarily?
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.
