True.

But it's not really even MarkDown and AsciiDoc that we're using here.

We've got nostr : nevent links, invoices, custom emoji, inline profiles, etc...

Time to also have clear definitions of these nostrified versions imo:.

- Ntext

- NDown

- NosciiDoc

Reply to this note

Please Login to reply.

Discussion

It's Nostr-flavored markup, but it's based upon Markdown or Asciidoc.

nostr flavored as in it recognises nostr: prefixed entities right? or are you supposed to use link: with those?

Yeah, it handles Nostr entities in a sensible manner, basically.

You can see how that works in my latest PR. The Nostr Markup logic is actually complex. That's how the problem of the disappearing links came about. I'm not disappearing them, with my parser, I just add an internal link behind them, and then the user is free to choose.

Sometimes external links are broken, after all, or you're someplace with slow Internet and avoiding websockets.

I've spent weeks figuring out how to do all of that stuff. Have a headache. 😂