Thread

I also markdown ALL THE THING. #[2] has strong feels about .md. 😅

Is there a nip for markdown? Should there be one?

I concur MD would be amazing

Damus used to support it, but it was removed because it was inconsistently implemented in different apps, and could allow for malicious links to be embedded in text.

I've really enjoyed it with logseq too

The new guy… 😉 #[0]

😂 it was like a mini block size war for a few days

😅

absolutely *love* obsidian and totally agree

We already had this debate. Markdown lost.

fun while it lasted

The good old days

You can use Markdown in long form content events, kind-30023 as defined in NIP-23, but not on kind-1 events, please. 🤙 https://github.com/nostr-protocol/nips/blob/master/23.md

😂💜🤙

Can someone explain to me like im a 5 year old what markdown us? I'm familiar with Obsidian and have been using it recently But I'm still learning about this space and everything going on 😅 I have a lot of research to do

😂

markdown is just a simple formatting language. You know how you can make a link by using brackets and typing [LINK TITLE](https://heres.the.url) Well a markdown compatible app will not show the brackets and the textual link, it will just show the bold & clickable LINK TITLE. There are a lot of other formatting tricks in markdown that you use in notes the * for italics, ** for bold, etc. That's really all it is, but doing any sort of formatting with text itself can end up causing conflicts and weird behavior sometimes, so despite markdown being available in a ton of different places, its not necessarily the best or even a good choice always. I'd be less knowledgeable about when and why markdown wouldn't be a good option, and I'm just really lazy and don't want to have to correct the formatting of notes that I always construct in Obsidian. 🤣

lol, it feels like you are speaking english but i know not what you attempt to communicate 🤣

Protocol says: - No markdown in social nostr. - Markdown allowed in blog nostr. You're welcome.

I didn't know there was a distinction. In Damus or Nostrgram, is there a way to delineate "social" vs "blog"? 🤔

In Nostr it ask data in json format. And there are 6 items it is necessary to past into it might be more and some clients might understand it or not but 6 is required. The “kind” is determining what type is you are passing and I think kind 1 is the basic notes we are using. These are also so new to me and trying to understand but that’s my understanding from the previous cryptic note is: “For these basic notes we are using here, you can’t use and we should’t be able to use it but there are other kind of data that can passed on NOSTR and in some of them you can use”. I might be wrong as I said I’m still trying to understand what’s going on here so keep that in mind :)

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.

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." https://github.com/nostr-protocol/nips/blob/master/01.md

Planning to publish something on Habla this weekend!

much appreciated. zapped 🙏⚡

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.

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.

My man… you must have missed the “markdown wars”. They were like 3 weeks ago, equivalent to a decade on nostr. Check this out, especially the note on protocol bloat by #[3] #[4]

#[7] has stated several times against using markdown in kind-1 notes.

markdown is plaintext so it is technically allowed

I've created an issue to get clarification on this point https://github.com/nostr-protocol/nips/issues/297

Yup #[4]

Reference please

#[3]

#[7]

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?

Thank you so much for this I'm going to keep researching it, but thank you Get zapped fool🫶

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: https://github.com/nostr-protocol/nips/blob/master/23.md