Nostr Web Client

Generally, any kind of event (note, reply, longform note, whatever) is only found on the relay that the original user published it to. If my short list of relays doesn’t overlap with those relays I will not see the event.

I think this is more of an issue in the short term for me since I was still signed up for the nostr.wine services a few days ago. Their service effectively broadcasts and retrieves events from a broader set of relays than I was subscribed to. Now that I am no longer using the service I am noticing that some of the events I was seeing and even some replies to my own events aren’t necessarily on my smaller set of relays.

I think part of the solution to this is clients getting smarter about where they broadcast and rebroadcast notes to especially when replying to a user that might not have much relay overlap with you.

Alexander 2y ago

Thanks for your response. I'm mainly using @plebstr (I hope this kind of tagging works). Do I know which relay I'm posting to? I didn’t know that I was posting to a primary relay.

Reply to this note

Please Login to reply.

Discussion

armstrys 2y ago

I have heard of #[3] but not used it! On nostr the experience is quite variable both in terms of features and customizability. Some clients like Damus allow you to customize your relay list but all your content goes to all relays. Others like Nos may let you publish content to a specific relay for each note, and others that want to be more user friendly may take the relay management piece completely out of the users hands. The nice thing is that as long as you have your private key you can test different clients though people have run into some issues like losing their contact list if you try to jump between some clients too quickly. There are tools to fix those issues so I wouldn’t let that dissuade you from exploring!

Alexander 2y ago

I didn't do it right. I had to tag #[4] by copy-pasting the public key from the account page.