Replying to Avatar Terry Yiu

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.
Avatar
jb55 7mo ago

I don’t think so, nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 switched us over to the proper list

Reply to this note

Please Login to reply.

Discussion

Avatar
Dikaios1517 7mo ago

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.

Avatar
Daniel D’Aquino 7mo ago

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.

Avatar
Dikaios1517 7mo ago

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!