See Below.
From: pablof7z<-DerekRoss at 06/11/23 08:17:01 on wss://atlas.nostr.land
CC: #[4]
CC: #[5]
CC: #[6]
CC: #[7]
>---------------
>You can’t search by subject (not 1 character),
I'm not sure what you mean by (not 1 character). Certainly a client can include the subject tag in a search. More-speech does that now.
>and you can find the tagged events for the threads snuck more easily and bulletproof via #e queries
#e queries are good when you want to search for notes that refer to other notes. However, I also want to search for notes based on the contents of subject (and the note itself). So I want to put any note with "CNN" in the subject into my "CNN" tab. I can't do that with an #e tag.
Login to reply
Replies (2)
I agree that CC and From is just duplications from a Nostr-native structures (#e, #p) and should not be rewriten in the reply note. There is no need for it.
This is really ugly.


> I'm not sure what you mean by (not 1 character). Certainly a client can include the subject tag in a search. More-speech does that now.
You can’t do #search filter as relays don’t index non-1-char tags
> #e queries are good when you want to search for notes that refer to other notes. However, I also want to search for notes based on the contents of subject (and the note itself). So I want to put any note with "CNN" in the subject into my "CNN" tab. I can't do that with an #e tag.
My point is you don’t need the subject tag everywhere, just on the OP; each reply you can get by #e:[OP’S ID]
Iirc the subject NIP doesn’t mention anything about replies having to copy the subject tag everywhere