they stuff it as JSON in the "content" field of a NIP-02 contact list message, mostly
Discussion
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.
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.
Coracle too
Can shared relay lists help find someone you follow if they’re banned from a mutual relay?
i mean, i suppose it could. some clients let you view people's shared relays. snort.social lets you do it, for example
"shared" as in published, not "in common with you", i mean
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.
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.
Thanks for the explanation. I’m guessing clients don’t actually do that yet tho?
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
I meant if clients read and write to your mutuals’ relays.
Gossip and Coracle do, Snort is working on it.
Yes, this.