I was like woooowww, but then I noticed that it often garbles the text and sentences from the original event content are just missing.
He's got markdown sort of smeared all over the place, with a really aggressive parser, and it just chews everything up.
Agree that Asciidoc is the best place for this.
I render it on everything, as I implemented it for Asciidoc, so why not, but it's usually like 80% hit. Push it much over that, and you start transforming stuff that isn't LaTeX because the parser has to start guessing.
Yakihonne at least puts it into inline-code backticks, so that you can find it.
Textstr.org is rendering stuff like this:
Which I find outrageous. I tried to render that and the parsing is a nightmare. I'll do it the way Yakihonne does, as that's not insane.
It comes down to having a clear, easy-to-parse, syntax, without a gazillion flavours.
#asciidoc is a good fresh start. Just have to mindful that Nostr-stuff has to added in a clear way most peeps ca agree on + all new WYSIWYG editors etc... have to built.
nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn was thinking we could build a plugin for Asciidoctor, to set a Nostr standard for the implementation. Then custom implementations could refer to that.
Could maybe get Asciidoctor to take it up on their own list.
We're working on the plugins already, might as well share them with the world.
