No underline
The problem with markdown.
I know there are years of discussion around this, yet it still wasn't added because of breaking changes.
I'll write a non-breaking stanrdard and implement in my projects. I'm tired of waiting.
Will share when it's done.
Login to reply
Replies (3)
> I'll write a non-breaking stanrdard
What about djot?
It's not another AsciiDoc if you meant that; it's more like a standardization of Markdown, mostly backward compatible. It aims to solve both ambiguities and DoS vulnerabilities that inevitably arise in parsers:
View quoted note →
It's already used in NIP-54 Wiki as well:

GitHub
nips/54.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
Sounds good.
Now I'm altering what I'm specing to be more dynamic rather than markdown focused, after considering djot more and your comments about it.
Currently adjusting the spec(s) to make it more dynamic rather than just making it for markdown only, and hopefully what'll come out of it will be decent and solves problems (at least problems to me, which is rigidness and centralization along with scattered non-standards / workarounds).