Asciidoctor is much more powerful and uniform than Nostrmarkup (that's what I call it). I just use NM for everything except 30041s and 30818s, where I use Asciidoctor and add in some Nostr-y stuff, like rendering npub handles.
We only defined a handful of tags, for NM, and everyone has already gone off and implemented them differently. GitHub can enforce GH Markdown because they control the app its displayed in, and if you don't format it like they say, it looks garbled.
yeah, nostrmarkup is much better than ndown 100%, but i like #nup because it's ironic in the same way that nostr is like no-stir
but i think your approach is better, asciidoc is more flexible, i think that what make it get more wings is to simply define a minimal spec that covers most people's needs, and then define that in a document that you make easily available to users to learn how to write it. they will write compliant asciidoc then, but don't need to know the deep features of it, while allowing them to go deeper if they want to.
I think the point of it won't be apparent until I start posting scientific papers with text that gets rendered like
I've also got it rendering stuff like
and
as a conniseur of technical things, i appreciate what you are saying.
Sorry, that should be
I mean, that proves my point. They blocked the media server, but if you pass it as Asciidoc, it gets rendered on-the-fly. Anyone who can see the event, can see the diagram.
I now think we'd end up with something similar to #asciidoc probably if we decided to start inserting stuff into GH markdown, so I'm fine with the choice.
Just a real PITA to build all new WYSIWYG editors for all this #complainstr 😉
