So you're going to request them to _not_ implement Markdown now? :)
Discussion
What clients implement Markdown? We should ask them to remove Markdown support. Or just leave the bold/italic stuff in place and remove the weird stuff like []() and ## === ![]()
Like this: https://github.com/styppo/hamstr/pull/12
Honestly all I really want is bold, italics, bulleted lists, and code blocks. If I can squeeze in quotes I'd take that too.
Snort
Astral
Damus
Probably more.
It's mostly the links and images I have an issue with TBH, and I don't see much need for headings. Lists still just look like lists in plain text so they don't bother me at all. Same with blockquotes (which I think is just a > ?)
Part of my issue with links and images is that they're not easy to strip from the text. I could parse the markdown and then strip the html, or write some regex that would strip it, but don't think it's right that clients that don't want to support it should need to do that.
Italics would slap 💯
It looks like Markdown was added to Damus just so links could be made clickable (the same reason I've stupidly added a Markdown parser to branle an year ago and it bubbled up to Astral), and someone there is working on removing it: https://github.com/damus-io/damus/pull/301
#[2] has also said he is going to remove Markdown support from Astral.
🫡
Time for a NIP that defines an acceptable markdown set?
Ok, this idea might be incredibly insane and stupid but hear me out… would it be possible to invent a form of markdown that uses null/whitespace characters as delimiters, that way it would just render normally in clients that don’t support it?
I guess the point is to keep the notes human readable? what about super long URLs linking to images? those often make the text content annoying to look at... I guess "all" clients agree to render those URLs as images...
