Protocol says:
- No markdown in social nostr.
- Markdown allowed in blog nostr.
You're welcome.
Discussion
I didn't know there was a distinction. In Damus or Nostrgram, is there a way to delineate "social" vs "blog"? 🤔
The first popular nostr clients are mostly social clients, including Damus, nostrgram, Iris, Amethyst, snort.social, etc.
These "notes" don't allow modifications nor markdown.
The protocol has defined recently a new use case that allows to use nostr to publish and distribute longer form content, as blog posts.
Some nostr clients/webs have started to be developed to support this use case.
i.e. https://habla.news
#[6] is working on it, if you are interested in following its development.
These "long form content" notes allow modifications and markdown.
Planning to publish something on Habla this weekend!
much appreciated. zapped 🙏⚡
It seems impossible to figure out how to get sourced on Habla.news. What does the client filter for, anything that looks like Markdown? I doubt it, but there's no apparent About or FAQ. #[5]
habla.news shows long-form content (kind 30023 events) in the relays.
As defined in NIP-23:
NostrGram has a "Blog" filter (click the ellipsis in the top menu bar and it's under General Filters). It filters for notes of at least 300 words.
Where does the protocol say "No markdown in social nostr"?
"1: text_note: the content is set to the text content of a note (anything the user wants to say). Non-plaintext notes should instead use kind 1000-10000 as described in NIP-16."
markdown is plaintext so it is technically allowed
I've created an issue to get clarification on this point
NIP-01 states:
1: text_note: the content is set to the text content of a note (anything the user wants to say). Non-plaintext notes should instead use kind 1000-10000 as described in NIP-16.
Markdown is plaintext so should be allowed. Paging #[6] for clarification.
#[7] has stated several times against using markdown in kind-1 notes.
Markdown syntax for links, footnotes and images is definitely not plaintext. The rest is tolerable. Please don't break it for all other clients or force everybody to support a cumbersome and heavy syntax with all the garbage that comes with parsers, plus the indeterminism as there are multiple flavors or Markdown, it's an endless shithole.
Did you know Twitter doesn't have Markdown support?