121 sats \ 7 replies \ @ek OP 10 Aug \ parent \ on: Crossposting format feedback meta
The spec explicitly mentions clients shouldn’t parse markdown content in kind 1:
1: text note: the content is set to the plaintext content of a note (anything the user wants to say). Content that must be parsed, such as Markdown and HTML, should not be used. Clients should also not parse content as those.
write
preview
89 sats \ 6 replies \ @WeAreAllSatoshi 10 Aug
Ah, gotcha. Is there a different kind that does allow it?
reply
33 sats \ 3 replies \ @WeAreAllSatoshi 10 Aug
Also, should not isn't as strong as must not lol
reply
0 sats \ 2 replies \ @ek OP 10 Aug
That’s true lol
reply
32 sats \ 1 reply \ @WeAreAllSatoshi 10 Aug
I guess again it feels like a client issue. Either detect and parse and render markdown, or also support other kinds that the spec allows to contain markdown 🤷‍♂️
reply
8 sats \ 0 replies \ @WeAreAllSatoshi 10 Aug
I don’t use nostr so I’m probably missing context, but maybe an uninitiated opinion is helpful
reply
26 sats \ 0 replies \ @jp305 10 Aug
30023? a few clients have formatting.
I always thought crossposting should be for long notes…
reply
100 sats \ 0 replies \ @ek OP 10 Aug
Yes, NIP-23 but people expect their content to show up in clients like Primal or Damus
reply