no, it's to tell the client what format of text is in the content field
this would end the bullshit about not allowing markdown in kind 1 notes, for example
Discussion
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
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. 😂
Yeah, I'm only building one editor, with a choice of Markdown or Asciidoc, as the basis. Why bother with plaintext? There is no such thing as plaintext.
1. This is *not* plaintext.
2. This isn't either.
3. You can write `anything` into a textbox.
:heart:
Also, who died and said you can't use [[wikilinks]] in every note?
plaintext is from the before time, before Smalltalk at Xerox PARC
as soon as it stopped being a dynamic version of a TTY there was no more plaintext
even TTYs got colours and styles and blinking and underline and shit, not long after the arrival of GUIs
As soon as you're like
* First of all
* Secondly
* And don't forget
It's markup. Someone can make that pretty, for ya.
