pull down to refresh

When markdown formatting on nostr?
1381 sats \ 13 comments \ @supratic 17 Feb 2024 nostr
Just wondering... why not?
write
preview
related posts
44 sats \ 5 replies \ @ek 17 Feb 2024 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.
reply
10 sats \ 0 replies \ @supratic OP 17 Feb 2024
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
reply
0 sats \ 3 replies \ @anon 17 Feb 2024
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.
reply
1031 sats \ 0 replies \ @supratic OP 17 Feb 2024
Was just a question, mate. Take it easy. Any particular reason to be anon on this topic?
reply
0 sats \ 0 replies \ @987654321 17 Feb 2024
What's Twitter?
reply
0 sats \ 0 replies \ @ek 17 Feb 2024
I think you replied to the wrong person
reply
10 sats \ 0 replies \ @nout 17 Feb 2024
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.
reply
10 sats \ 1 reply \ @WeAreAllSatoshi 17 Feb 2024
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.
reply
10 sats \ 0 replies \ @anon 17 Feb 2024
Wut? If people use it when they produce content, clients are forced to use it when rendering that content.
reply
10 sats \ 3 replies \ @w3irdrobot 17 Feb 2024
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.
reply
1111 sats \ 1 reply \ @ek 17 Feb 2024
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.
reply
519 sats \ 0 replies \ @w3irdrobot 17 Feb 2024
damn. roasted. haha thanks. seems ridiculous that markdown would be called out to not be parsed. perhaps it's an xss attack mitigation
reply
20 sats \ 0 replies \ @supratic OP 17 Feb 2024
deleted by author