And yes it's based on kind 3 events, but not the P tags (that's contacts) but the relay list held in the note content.
I've actually been wondering that myself. For the client I'm writing, if you're replying, I have it use the first relay the client discovered the note you're replying to. For new notes, I just use the first one in the list.
When you update the relays in the client you're using it puts a record of it in nostr.
Hey #[0] if you're wanting to see which relays you should use, check out the updated Nostrum Search list @ https://nostrum.pro/search/#relays
I'll have an update on the Nostrum search engine in an hour or two that will show you the relays with the largest number of users, which should help you make a decision about which ones to keep.
Threw together the Nostrum Search Engine today. Has about 200k notes in its index and gathering more in real time so the results are fresh and from a big list of popular public relays. Let me know what you think.
https://nostrum.pro/search/index.html
#[0] #[1]
I always hated about Twitter that searching for a tweet you remember was nearly impossible, and Google wasn't any better most of the time. So Nostrum Search was born. :)
Threw together the Nostrum Search Engine today. Has about 200k notes in its index and gathering more in real time so the results are fresh and from a big list of popular public relays. Let me know what you think.
https://nostrum.pro/search/index.html
#[0] #[1]
A bunch of things to add, like better profile loading for images and filters for dates and specific pubkeys etc. It's coming.
Threw together the Nostrum Search Engine today. Has about 200k notes in its index and gathering more in real time so the results are fresh and from a big list of popular public relays. Let me know what you think.
https://nostrum.pro/search/index.html
#[0] #[1]
Probably a couple of weeks. I have a lot of functionality to add and I'm trying to make each addition as smooth and user-friendly as possible. Performance is really good and the UI is user-friendly. Coming along very nicely and looking forward to your feedback when ready!
Sorry Derek, wasn't supposed to tag you. Bug. :)
Testing Nostrum. Replying to myself with an embed and a tag. #[2] #[3]
Embedded note test.
#[1]
That's why I'm using Twitter's method for threads. You see the first level replies only and have to click to see replies to that reply. I'm also going to implement a "see more replies" link after a fixed number of replies, also Twitter-like.
I can see that as the default behavior, but not requiring that they all remain tagged. I only noticed b/c I got a reply in my notifications that wasn't directed to me at all. I was further up the chain and still got a notification. I can see it becoming a real nuisance. I'll be introducing a Twitter-like option to not receive notifications of replies to a particular thread to prevent that. Might be a good idea for Astral too.
Yeah I find it odd. I'm not allowing the removal of the tag to the author of the note you're replying to, but I'm letting the others be removed. I don't see any reason not to. I wasn't including them at all until I saw that in the nip. Seems to me the only person that should be automatically tagged is the original author.
Thanks Derek. Much appreciated!
What's the thinking behind nip10 saying all p tags should be included in replies? If I'm replying to a single individual's comments, why include everyone up the chain if they're not involved?
"When replying to a text event E the reply event's "p" tags should contain all of E's "p" tags as well as the "pubkey" of the event being replied to." https://github.com/nostr-protocol/nips/blob/master/10.md
#[0] #[1]
Tagging myself #[1]