Just testing something...
- [Alby](https://getalby.com/)
Discussion
It worked?
No markdown.
I think it depends on your client/UI. In nostrgram.co the markdown works great. Going to check on Damus
Amethyst doesn't show it. But NIP-01 specifies text only, so don't you start ruffling #[5] 's feathers.
Text can still have a mimetype
That's not a solution, not even close. That's the creation of a new problem.
Not claiming that to be a solution, just pointing out that no one can stop clients from doing that and thus putting whatever content type they want on a note, just like it happened with inscriptions.
The threat of a potential contentious NIP like that might put pressure into supporting markdown in a more sane way.
Sure, clients can do anything, that includes things that are much worse than Markdown. No protocol will survive if everybody starts to do awful things -- or if a single dominant client does "embrace and extend" techniques. Nostr is very fragile.
However the Markdown issue often happens because client makers want a way to automatically turn URLs into links, so they add Markdown libraries, not realizing the evil that would bring, so what I am doing is telling them.
Do you have any long form anti-markdown rants I can look into? I want to understand
https://github.com/jonathanleger/nostrgram/issues/1
Let's see if #[0] will be cooperative.
I think a good solution is for NostrGram to convert any markup put into the notes created in it into normal text+links before submission to the relay. The only exception being italics and bold, which are very simple and I'll leave in.
I only have NostrGram supporting a limited amount of markup (link, image, bold, italic) so it shouldn't be difficult to "clean up" posts from users while still having NostrGram show the markup should a note come in from a relay that has it. Since nobody can control what goes into the relay, I don't want to mess up the user experience should markup appear that's beyond my control.