Nostr Web Client

Why include the body of what you’re responding in emails’ broken format of > quotes? A tagged event already provides the quoted text in a far superior/structured way

This looks broken

unclebobmartin 2y ago

See Below.

From: pablof7z<-DerekRoss at 06/11/23 07:57:53 on wss://atlas.nostr.land

CC: #[4]

CC: #[5]

CC: #[6]

CC: #[7]

>---------------

>Why include the body of what you’re responding in emails’ broken format of > quotes?

I do that so that I can respond to questions and statements in a structured way. Most of nostr is clinging to a twitter mindset where notes are one or two sentences long. I have hopes that nostr will grow beyond that kind of limited thinking and allow very salient in-line discussions.

>A tagged event already provides the quoted text in a far superior/structured way

The tags help the clients to construct the threads; but the tags do not help the reader understand which part of a note the responder is referring to. Again, the twitter mindset is a tough habit to break; but one that I think we should break as soon as possible.

>This looks broken

I agree that it looks broken. Looks are the responsibility of the client.

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 2y ago

If you do >SPACE instead of just >, we can treat it as markdown and render it better.

unclebobmartin 2y ago

From: -VitorPamplona<-D... at 06/11/23 09:42:15 on wss://atlas.nostr.land

CC: #[4]

CC: #[5]

CC: #[6]

CC: #[7]

CC: #[8]

>---------------

> If you do >SPACE instead of just >, we can treat it as markdown and render it better.

You mean like this?

PABLOF7z 2y ago

You can perfectly do that and in fact you could argue that’s one use case of highlighter.com; I see myself doing that to pull out specific things to reply to on kind 1s.

But including the whole content you’re replying to embedded in the content looks bad and breaks the structured data formatting of nostr events (increases parsing complexity/ambiguity).

Why not create specific event kind:1 tagging the content you’re replying to and allow threading to do its magic?

Vitor Pamplona 2y ago

Or just reuse highlighter's event kind as a quoted event inside the kind 1. It would be awesome

PABLOF7z 2y ago

Exactly

unclebobmartin 2y ago

From: -VitorPamplona<-D... at 06/11/23 10:18:15 on wss://atlas.nostr.land

> Or just reuse highlighter's event kind as a quoted event inside the kind 1. It would be awesome

Why would I want another event kind when I can simply edit the contents in place, like this. Remember, I'm not using a phone. I'm sitting at my keyboard, and I have a very large screen. Nostr needs to play well in the desktop environment as well as the mobile environment.

CC: #[4]

CC: #[5]

CC: #[6]

CC: #[7]

CC: #[8]

PABLOF7z 2y ago

Why make the experience of interacting with your content via a phone painful when you can make it not so? 🤷‍♂️

PABLOF7z 2y ago

Interoperability are one of nostr’s superpowers and this mode of creating events it is detrimental to it

unclebobmartin 2y ago

From: pablof7z<-DerekRoss at 06/11/23 10:57:42 on wss://nos.lol

> Interoperability are one of nostr’s superpowers and this mode of creating events it is detrimental to it

No it's not. There is no rule about the structure of the content of events, nor should there be. Any use can put any damned thing they want to into the contents of their kind:1 events. It's a free nostr! Clients have to live with that.

CC: #[4]

CC: #[5]

CC: #[6]

CC: #[7]

>---------------

PABLOF7z 2y ago

I’m sorry, but “nostr is free, i do what I want” is a cop-out.

unclebobmartin 2y ago

From: pablof7z<-DerekRoss at 06/11/23 10:56:47 on wss://nos.lol

> Why make the experience of interacting with your content via a phone painful when you can make it not so? 🤷‍♂️

I am not making the experience of interacting with my content painful. Any pain experienced by the users is due to the client they are using. Some clients will try to parse markup languages. Some won't. Some will try to infer the structure of a note from the paragraphs, others won't. Que Será, Será.

CC: #[4]

CC: #[5]

CC: #[6]

CC: #[7]

Vitor Pamplona 2y ago

Because everyone else that reads your posts has a phone, not a large screen. And again, it's just an ugly.

By having a separate highlight event for each quote, you are allowing people to copy, like, zap, report the quoted sections directly. That's the power of nostr. Composability.

unclebobmartin 2y ago

From: -VitorPamplona<-D... at 06/11/23 11:03:14 on wss://relay.nostriches.org

> Because everyone else that reads your posts has a phone, not a large screen.

No, not everyone. I think it would be a disaster for Nostr to assume that mobile device was the only allowed terminals. Indeed, who knows what form mobile devices will take in the future. It may be that we will all soon be wearing Vision Pro goggles with really huge virtual screens.

> And again, it's just an ugly.

Ugliness is in the eye of the beholder.

> By having a separate highlight event for each quote, you are allowing people to copy, like, zap, report the quoted sections directly. That's the power of nostr. Composability.

From my point of view the power of nostr is freedom. Feel free to compose all you like. I will feel free to compose as much as I like. I may decide to adapt to the highlighter style of quoting; and I may not. Or I may decide to use both in different use cases. It's a free nostr.

CC: #[4]

CC: #[5]

CC: #[6]

CC: #[7]

CC: #[8]

unclebobmartin 2y ago

From: pablof7z<-DerekRoss at 06/11/23 10:16:11 on wss://atlas.nostr.land

CC: #[4]

CC: #[5]

CC: #[6]

CC: #[7]

>---------------

> You can perfectly do that and in fact you could argue that’s one use case of highlighter.com; I see myself doing that to pull out specific things to reply to on kind 1s.

That may be.

> But including the whole content you’re replying to embedded in the content looks bad and breaks the structured data formatting of nostr events (increases parsing complexity/ambiguity).

It's up to the author if they want to include the whole content. It's easy enough to edit out the things that don't apply.

> Why not create specific event kind:1 tagging the content you’re replying to and allow threading to do its magic?

Oh I think we should all do that. More-speech certainly does. I just don't think that's sufficient for the application of discussion topics and debate.