When markdown formatting on nostr? \ stacker news ~nostr

1381 sats \ 13 comments \ @supratic 17 Feb nostr

Just wondering... why not?

44 sats \ 5 replies \ @ek 17 Feb freebie

You need to be more specific. Long-form content as specified in NIP-23 already supports Markdown. See habla.news. You mean short text notes? NIP-01 explicitly mentions that clients should not parse those as HTML or Markdown:

Content that must be parsed, such as Markdown and HTML, should not be used. Clients should also not parse content as those.

Why that is I don't know, I can only speculate and I'd rather not.

10 sats \ 0 replies \ @supratic OP 17 Feb

Yes, I mean NIP-1, the most used one! I also assume most of the work is done on the client side and how to render the string contained on it!

I was wondering why NIP-23 yes and not (yet) on NIP-01

0 sats \ 3 replies \ @anon 17 Feb

Twitter doesn't do markdown, why aren't you whining to them?

Allowing markdown excludes text-only clients and forces GUIs on people. Obviously you don't care about that, but a lot of people do. Get over it.

1031 sats \ 0 replies \ @supratic OP 17 Feb

Was just a question, mate. Take it easy. Any particular reason to be anon on this topic?

0 sats \ 0 replies \ @Nuttall 17 Feb

What's Twitter?

0 sats \ 0 replies \ @ek 17 Feb

I think you replied to the wrong person

10 sats \ 0 replies \ @nout 17 Feb

Some clients like Amethyst supported it initially, but it was frowned upon and it got removed for short notes. Having formatting results in a different type of content being posted and I think I agree it makes sense to only do formatting for long form notes.

10 sats \ 1 reply \ @WeAreAllSatoshi 17 Feb

Yea, this seems like a client thing, not necessarily a protocol thing. Kinda like how on SN, GitHub, etc, it supports markdown, but that doesn't mean you have to use it.

10 sats \ 0 replies \ @anon 17 Feb

Wut? If people use it when they produce content, clients are forced to use it when rendering that content.

10 sats \ 3 replies \ @w3irdrobot 17 Feb

there's not particular reason clients couldn't just support it. even nip1 is just text. afaik the nips don't specify how to treat it. if they do, that seems ridiculous. just parse it as markdown.

1111 sats \ 1 reply \ @ek 17 Feb

afaik the nips don't specify how to treat it. if they do, that seems ridiculous. just parse it as markdown.

NIP-01 does though.

Content that must be parsed, such as Markdown and HTML, should not be used. Clients should also not parse content as those.

519 sats \ 0 replies \ @w3irdrobot 17 Feb

damn. roasted. haha thanks. seems ridiculous that markdown would be called out to not be parsed. perhaps it's an xss attack mitigation

20 sats \ 0 replies \ @supratic OP 17 Feb

deleted by author