You should do that on the e and p tags, not on the text, like social clients do. You can see who you are replying to and remove it on amethyst without having to pollute the text.
Discussion
From: -VitorPamplona<-D... at 06/11/23 10:35:39 on wss://relay.nostriches.org
> You should do that on the e and p tags, not on the text, like social clients do. You can see who you are replying to and remove it on amethyst without having to pollute the text.
I don't mind "polluting the text" because I don't consider it "pollution". I also don't think the e and p tags are sufficient to give me what I want. And...it's a free nostr; what I _should_ do is up to me.
CC: #[4]
CC: #[5]
CC: #[6]
CC: #[7]
CC: #[8]
Since I coded the same thing you have with e and p tags, I think you are wrong. And I don't even have the power of a desktop toake it work.
From: -VitorPamplona<-D... at 06/11/23 11:07:47 on wss://relay.nostriches.org
> Since I coded the same thing you have with e and p tags, I think you are wrong. And I don't even have the power of a desktop toake it work.
It is your right to think I'm wrong. It's a free nostr. It is my right to persist in my wrongness. It's a free nostr.
CC: #[4]
CC: #[5]
CC: #[6]
CC: #[7]
CC: #[8]
Yep, you do you. Just know that posts from your clients look very ugly and difficult to read in all others.
From: -VitorPamplona<-D... at 06/11/23 11:24:22 on wss://relay.nostriches.org
> Yep, you do you. Just know that posts from your clients look very ugly and difficult to read in all others.
I look at that screenshot and I think: "My, how lovely!".
Anyway, I'd like to thank you for this discussion. I actually have been listening to you. It's just that it's been so long since I've had a good debate on a free social network that I couldn't resist poking the bear a little.
>
CC: #[4]
CC: #[5]
CC: #[6]
I mean that’s obvious, no one is arguing that you should be restricted in any way, we’re discussing best approaches, but the “nostr is free, I’ll do what I want” is certainly a conversation stopper.
The same way you consider the Twitter way of thinking lacking creativity I think this way of email-thinking is falling short of what it could be.
Fwiw I agree with the idea of using nostr content in ways way beyond the Twitter use case and in particular I’m interested in the email-like mode (I wrote an email client when I was a 12 so I’ve always been very interested in the format)
From: pablof7z<-DerekRoss at 06/11/23 11:14:37 on wss://nos.lol
> ...The “nostr is free, I’ll do what I want” is certainly a conversation stopper.
Good. I'm glad you figured that out.
CC: #[4]
CC: #[5]
CC: #[6]
CC: #[7]
Lol, you could have said so from the beginning!
🙌
From: pablof7z<-DerekRoss at 06/11/23 11:33:58 on wss://nos.lol
> Lol, you could have said so from the beginning!
>
> 🙌
What fun would that have been? Be well.
CC: #[4]
CC: #[5]
CC: #[6]
CC: #[7]
I’m fine with the early email style responses, I’ve always thought it was a good format, but could you perhaps change the header? Maybe don’t include the relay, time, or CCs since those can more easily be embedded in the event instead of the content?
From: (jsm) at 06/11 11:38
> I’m fine with the early email style responses, I’ve always thought it was a good format, but could you perhaps change the header? Maybe don’t include the relay, time, or CCs since those can more easily be embedded in the event instead of the content?
I've shortened the header significantly. And I've moved the CC:s to the end. For the time being I want to leave the CC:s in place because I don't want to create a horrible UI with checkboxes to select who should be mentioned. I just edit the list and the mentions tagged accordingly.
CC: #[4]
CC: #[5]
CC: #[6]
CC: #[7]
CC: #[8]
Thank you, that looks so much better.
What about changing the more-speech UI to allow editing the list of CCs that goes into the event as text instead of doing that editing in the content? It seems like you’re editing the content so you can edit the tags instead of editing the tags themselves.
> What about changing the more-speech UI to allow editing the list of CCs that goes into the event as text[...]
Editing text with a keyboard and mouse is pretty easy. I am really loath to create a special UI with a bunch of checkboxes for each CC.
In this thread I've been leaving all the headers and CCs in place because the thread was _about_ those headers and CCs. Typically, however, I simply ^A and delete them before I start composing. In this reply, for example, I simply editted out the header and CCs.
That looks much slicker and doesn’t include any repetitive information that clients already show.
What I meant for the CCs is editing the CCs in a separate text field (no annoying and slow checkboxes) as plain text and then using that separate text to change the tags instead of doing the editing in the content field.
From: jsm<-DerekRoss at 06/11 14:08
> What I meant for the CCs is editing the CCs in a separate text field (no annoying and slow checkboxes) as plain text and then using that separate text to change the tags instead of doing the editing in the content field.
Or... Perhaps clients who don't want to show CCs can remove them...
This is what a reply looks like without the headers and CCs. ^A and we're off to the races.
🤙🤙 you too 😊