I wish Nostr clients tried to render posts as markdown… that’s what scuttlebutt does, it’s not perfect, but it does allow inline formatting and embedding images / links. Full html seems like too much, plaintext is limiting. Markdown is flawed but works.
Discussion
But Twitter is plaintext!
To require Markdown is a giant bloat imposed on everybody. And if a client doesn't support it the plaintext fallback is horrible and unusable (contrary to Markdown's own claims).
Another option is to go like email and let people post with multiple alternative encodings of their content, plaintext, md, and html…
Personally I really like what you can do with formatting in markdown in scuttlebutt.
More I think there’s lots of interesting things you could do with collaborative document creation using CDRT’s where you scoped who could contribute based on your social graph. That kind of document would need some formatting.
Sure, I agree. I think we should have other standard formats, but in other contexts (and probably other apps dedicated to them -- not that they couldn't be merged into "social" apps too if client developers wanted), using other event kinds, not the basic most simple Twitter-like kind-1 notes.
Twitter was plaintext because we had to make it work over sms! ;-D
160%
If SMS supported Markdown then Twitter would have been a failure.
I think markdown would get abused and you’ll have inconsistencies in app aesthetics that can ruin the feel of a well designed unified experience.