Not all devs are like this, but many devs grew up experiencing negative social situations which led them to spend time with computers rather than with people.

If this pattern persists, devs often grow to be extremely out of touch with normies, leading to the exact issue you pointed out with respect to “Markdown”, whatever that is.

The answer is for devs to test group their stuff using normies. When a dev watches just how little normies know the dev is more likely to realize that their work doesn’t end at coding. It ends when a bridge has been built that normies can walk on.

have you looked at asciidoc?

i am using it on my docs in my repos now, for one major reason being that it has an actual working built-in table of contents, and its tables are sane and readable without being rendered, the links are simple to understand: link:http://example.com[display text] and it lets you do a bunch of other cool stuff, the quoted preformated text is just two spaces indent though also you can use many of the more familiar things like backtick fences and single backticks `like this`

we will be using it as a standard for #alexandria because that is a book oriented application, also, so, it will happen

long form nostr posts have kinda not really caught on because the clients are crappy and actually without a reward people are not that interested in doing anything other than short notes

but it would be nice to be able to at least do sections, headings, quoted source code type blocks, and similar, for discussions

Just had a look at the event. I think what happened is the syntax was off so Ditto ignored it—but Primal has some logic to still render when the syntax is off, but in this case it went a little kooky on the render pushing a preview with Mike as the author.