Oddbean new post about | logout
▲ ▼
Vitor Pamplona | 20 days ago (raw) | root | parent | reply | flag 
 Checks the nip5 domain every 5 mins and downloads updates instantly
▲ ▼
Uxellodunum | 20 days ago (raw) | root | parent | reply | flag 
 Thanks for the response.
Humm... 🤔 
In that case I need to figure out why my Amethyst relays aren't updating accordingly.
▲ ▼
Vitor Pamplona | 20 days ago (raw) | root | parent | reply | flag 
 What do you mean? Is the list itself outdated? What's the issue?
▲ ▼
Uxellodunum | 20 days ago (raw) | root | parent | reply | flag 
 NIP05 has the optional relay list which can be pulled for users - Does Amethyst support this?
If so, yes my list is outdated. It was updated on my .well-known/nostr.json some days ago, and Amethyst hasn't pulled the updated list yet.
▲ ▼
Vitor Pamplona | 20 days ago (raw) | root | parent | reply | flag 
 That is just used to get your home relays. We only use that if we cannot get your nip 65 relays from our bootstraping relays. Your nip-65 should be sent everywhere and thus it should be on our bootstraping relays too.
▲ ▼
Uxellodunum | 20 days ago (raw) | root | parent | reply | flag 
 Ahh, I see, that makes sense and clarifies my confusion - Thanks.
What's the recommended way of updating the NIP-65 list?
Just setting the relays in a client that supports pushing the updated NIP-65 list to relays?
▲ ▼
Uxellodunum | 20 days ago (raw) | root | parent | reply | flag 
 I see metadata.nostr.com also uses kind 10002, so that should be a good starting point.