Replying to Avatar nout

I like using it for small code snippets, like `thisCall()`. The clients should make it (optionally) the least obtrusive, e.g. I'd recommend H1-H6 header font sizes to be all the same and maybe just do color/shade or font-weight (that's what Stacker News does).

Some parts of the spec work without issue already, for example

- this is

- a markdown list,

- but it works well in plaintext too.

#[3] #[4] for consideration. WDYT?
Avatar
fiatjaf 3y ago

Very sad.

I think it is fine to use it to render lists, literal URLs and `code`, but when you get to title case and, God forbid, stuff like `[name](url)` or `![what](image-url)`, then it will be a very sad day for Nostr.

Reply to this note

Please Login to reply.

Discussion

Avatar
nout 3y ago

Yeah, I actually agree with that. Lists, code, render headings with same font size to discourage those, and completely ignore url and image syntax.

Also we have listed almost all markdown syntax already (for the common markdown). It's not a long list...