not quite sure everyone understood the question i asked earlier about Nostr relays, because i WASN'T describing a scenario with no relay overlap.
rather, the scenario i was asking about was this:
John: i made a post. i talk to relays A and B.
Pete: i'm sharing John's post,. i talk to relays A, B and C.
Charles: i talk to relay C only. can i see John's post, since Pete is sharing it?
Yes that's how it works. When you repost a note you're publishing it to all the relays that you write to. It extends the reach of the note.
its a quite novel solution to content propagation, if we had a way to find npubs relays like a dht then we likely could find everything
I use nostr.watch to find relays.
I also run my own uncensored relay.
yep but clients should be automatically finding relays for npubs not on the same relays
manually managing relays struck me as one of the least user-friendly aspects of setting up my clients. they came with defaults, yes, but different ones, so i'd have different views of Nostr depending on which one i was using, until i "synced" them all using the shared list that's stored in the profile metadata.
also writing to 10 to 20 relays is not efficient
and further, i see that clients offer you the option of rebroadcasting any post you come across - not only your own posts, but any post - to all of the relays you're connected to. doesn't this imply that clients can copy posts between relays? if so, the next question is: does this happen when a client shares a post also? doesn't the client then expose that post to all the relays it's connected to?
we need a way to find and connect to users relays we arent using
