Replying to Avatar Anthony Accioly

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9u2mk7fe apologies for bothering you (just checking in with the most active committer to NIP-17). Where does Amethyst publish kind 10050 lists? Does it send a copy of the list to the relays listed in the Kind 10050 itself? Does it also send a copy to the user’s Outbox relays? Anywhere else?

https://github.com/nostr-protocol/nips/blob/master/17.md

#asknostr #nip17 #dmRelaysList

All the user's outbox relays + All indexer relays (kind: 10086) + all the ~300 connected relays at the time.

The function is called sendLiterallyEverywhere :)

More info in the sspecial relay lists for indexers https://github.com/nostr-protocol/nips/pull/1985

Reply to this note

Please Login to reply.

Discussion

Thanks sir. Things have definitely improved. For example, some of Haven’s relays reject this kind, but now I’m only seeing one error per relay instead of continuous write attempts like before. So I assume Amethyst is no longer retrying writes if some of the user’s relay rejects the list, correct?

It tries 3 times. If it can't do it, then it gives up.

Just to confirm. Does it give up writing this specific event or does it give up on the relay altogether? I.e., if one of my outbox relays rejects a kind 10050 3 times in a roll, but happily takes kind 1, answer to REQ, etc, will Amethyst still try to write my kind 1 notes?

Just the write of this event.

Brilliant. Thanks again.