Nostr

This would be like giving 4x blocksize increase along with SegWit: they will still hard fork and call you names.

In this case there are no shitcoiners, just Damus and Snort supporting Markdown and encouraging bad behavior. Astral and Hamstr have already removed theirs.

And I believe Damus and Snort they did it unwillingly. So we just have to ask them to remove support for the annoying Markdown parts and the problem is solved. Damus has a PR already. I tried to look at the Snort to submit a patch but couldn't find a place in their Markdown library to disable the annoying links.

DETERMINISTIC OPTIMISM 🌞 2y ago

LOL the 4x analogy.

I think ppl will still send markdown even if doesn’t get rendered because there will always be some client that might render.

I don’t see a good way for the markdown long content to coexist gracefully on the same relay without a kind for filtering by clients that may not be that sophisticated.

Reply to this note

Please Login to reply.

Discussion

fiatjaf 2y ago

Do you agree with me that bloating the protocol by requiring Markdown is an undesirable outcome?

DETERMINISTIC OPTIMISM 🌞 2y ago

I think giving clients a hint that “this text content may have inline formatting” is not bloat, it’s efficient.

Now, expanding that into adding a type field where the author indicates md,txt,html,etc is also a good idea, but that’s debatable.

fiatjaf 2y ago

Well, if 99% of the clients do not support Markdown then no one will be incentivized to write Markdown. It would be like some crazy person writing Markdown on Twitter.

fiatjaf 2y ago

Also, time is on our side. Currently all Nostr users are nerds who think writing Markdown is the epitome of human wisdom and feel very proud to have memorized that horrible syntax, but once normal people start joining they won't care at all about Markdown and will just write plaintext like they should.