i think that you could easily write a script that scans a post for signs of being markdown and renders it as such if it finds more than a few instances of `\n## something` and ` some quoted shell command' sorta things.
the way that my post got utterly mangled using 4 space prefixed references to filesystems the thing is unreadable on coracle.
at least to have a checkmark at the bottom of the input to tag it as long form type note so the interface doesn't turn it into a giant poo like that one here.
We should probably add a new event kind that is markdown, that's probably the best way to handle it. Or clients could support "rich text" mode and publish 30023's, but that would cause other problems.
What's the problem with 30023 that wouldn't affect a new event kind?
They're assumed to be blog posts, so to start publishing short notes with that kind would screw up long-form clients
and coracle assumes that all posts are what exactly? and why can't i write long form in this?
should i be moving to use another client?
I assume Coracle would handle this correctly, but the implication is that "blog reader" type clients would start seeing people's short social media posts in their feeds which is not the sort of content they want, even though it's the same nostr kind. Separating it into its own kind (even if the contents are compatible) would prevent this bleed over.
i see, so the spec doesn't have an opinion about short form having markup and i'm just having trouble trying to understand why rendering if found would be a problem.
i've been writing every length of form in markdown for a long time and have been wishing since at least 2016 that it was just a standard thing to *italicise* and **bold** and _underline_ and
- make
- lists
and quote things
that are probably from a terminal
because i am constantly needing all these things.
i don't use headings so much, that's more of a structured long form document, and for those, it's been a really long road to table of contents showing the outline to be normally available somewhere (github now puts them at the top of a markdown document rendering.
i'm keeping my ear open to hear about when markdown formatting comes to short form messages because, it predates even 2015, actually, once upon a time before markdown there was bbcode.
it was the silos that siloed users away from this.
