Nostr Web Client

Peter Gerstbach 2y ago

I am confused. Can somebody enlighten me how Nostr clients share relay lists (if they do at all)?

There seems to be various abandoned attempts, but nothing final.

NIP-23a/b/c: Abandoned and number reused for something else

NIP-26: Abandoned and number reused for something else

Then there are some implicit ways like

NIP-01: Defines kind-2 events to recommend relays

NIP-02: Defines kind-3 contact lists which could be used to decide which relays to read

Then there is this quite new draft:

NIP-65: Relay List Metadata by #[6]

Is this the one???

Have I missed something? Maybe some client developers can point me to the right direction? #[1] #[4] #[2] #[5] #[3]

Thanks! 💜

Reply to this note

Please Login to reply.

Discussion

Thorwegian 🇳🇴 2y ago

they stuff it as JSON in the "content" field of a NIP-02 contact list message, mostly

Thorwegian 🇳🇴 2y ago

they *should* be using a NIP-65 relay list metadata event but since it has such a high number, i'm assuming it was introduced relatively late, so hardly anyone clients use it.

Peter Gerstbach 2y ago

It seems #[1] started publicly a PR about feed advertisements in February which was commited as NIP-65 on Feb 7. So yes, it is quite new and I suspect this is the thing how clients should be doing it in future, right?

It is, obviously, supported by gossip, and it seems at least also by Snort. I haven't found anything about other clients but might have missed something.

Mike Dilger ☑️ 2y ago

Coracle too

bot 2y ago

Can shared relay lists help find someone you follow if they’re banned from a mutual relay?

Thorwegian 🇳🇴 2y ago

i mean, i suppose it could. some clients let you view people's shared relays. snort.social lets you do it, for example

Thorwegian 🇳🇴 2y ago

"shared" as in published, not "in common with you", i mean

bot 2y ago

I thought that was their purpose, it should be anyway. I’m just not sure how it would work, but I feel like it should notify you or something.

Peter Gerstbach 2y ago

The idea of NIP-65 is that you publish your read & write relays, so others can post to your read relays and read from your write relays. That should make it possible that you don't need mutual relays, which are anything but decentralised.

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

bot 2y ago

Thanks for the explanation. I’m guessing clients don’t actually do that yet tho?

Thorwegian 🇳🇴 2y ago

based on trying to capture NIP-65 in my Nostr indexer: there are clients that do it, but it's nowhere near as common as stuffing relay lists in the "content" field of a NIP-02 record

bot 2y ago

I meant if clients read and write to your mutuals’ relays.

fiatjaf 2y ago

Gossip and Coracle do, Snort is working on it.

fiatjaf 2y ago

Yes, this.

9839a36d... 2y ago

Mostly there are stored in the content of an kind 3 event as json.