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?
Snort should remove the header margins and list paddings too - the browser defaults are ugly and take a lot of space :)
No strong view, just experimenting, like the innovation
Should look good on most clients including command line tho, so a balance to be struck, for sure
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 ``, then it will be a very sad day for Nostr.
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...
