It is the preview of the message because you’re constructing it in a way this world be incredibly difficult for a client to parse all this ambiguous text into something sensible
Check out nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn ‘s coracle or nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c ‘a gossip to see how they allow you to, natively, add/remove p tags
* purview
From: pablof7z<-DerekRoss at 06/11/23 10:35:06 on wss://relay.damus.io
> ...you’re constructing it in a way [that makes it] incredibly difficult for a client to parse all this ambiguous text into something sensible.
It's a free nostr, you don't have to parse it. I'm certainly not parsing it.
The bottom line is that there are going to be a vast number of different clients. Each client will be pursuing it's own particular use cases for nostr. Some of those use cases will be relatively incompatible with others. C'est la vie! The last thing we want is some kind of fixed UI standard that every client must adhere to. Such a standard would almost certainly restrict the number of possible use cases and make nostr a lot less free.
So, if you don't want to propogate the subject tag, don't propogate it. If you don't want to parse the embedded replies, don't parse them. If you want to use highligher, use highlighter. It's a free nostr.
CC: #[4]
CC: #[5]
CC: #[6]
CC: #[7]
CC: #[8]
CC: #[9]
Gossip used to do this, but somehow it got lost in the UI shuffle. I would like to see it come back one day, the ability to at least untag those people you mention in the note, so they aren't alerted that you are talking about them.
From: mikedilger at 06/11 17:50
> Gossip used to do this, but somehow it got lost in the UI shuffle. I would like to see it come back one day, the ability to at least untag those people you mention in the note, so they aren't alerted that you are talking about them.
#[4] made a recommendation that I'm giving serious thought to. His idea was to put the CCs into a seperate text edit window so that they can still be editted by the user, but are not textually included in the message.
I can see the logic behind that. The CCs in the text can be an annoyance to those who are viewing messages on a smaller screen. On the other hand, the inclusion of CCs in written communications is traditional in the extreme, and has a very deep utility. It is good for people to have the CC list thrown in their face so that they realize whom they are communicating with -- and about.
CC: #[5]
CC: #[6]
CC: #[7]
CC: #[8]
CC: #[9]
CC: #[10]
But most clients already display the CCs when they display the p tags natively in the client. Perhaps if you’re on a client that doesn’t already show that information it might be helpful but maybe a better solution would be to display more information about the event rather than duplicating it in the content and tags.
