It's definitely no longer plain text, if you interpret it as a code snippet/preformatted text.
But as hodlbod pointed out that line has kind of already been crossed with link previews, event and npub references, so *shrug*.
Might as well go full markdown imho. Would be easy to have a content type flag to say "this was MEANT to be markdown". Since markdown is perfectly readable as plain-text too, I think it's reasonably backwards compatible.
Full markdown would be fine, if markdown didn't include things like link aliases, tables, and image embeds, because most markdown can be interpreted as plaintext (it's human-readable with no processing).
I mean I think every client is already processing image embeds anyway. markdown tables are human readable (nice to look at in plain text, even!).
Link aliases is probably the one that shouldn't be supported.
Markdown tables can be ok if you are using monospaced font, but if you don't align the pipes or have line breaks they're an absolute monstrosity
Ah that's true.
At the very least, supporting *emphasis* **emphasis** and block quotes in addition to the preformatted text you already do (on opt-in posts) would be nice. Since you're fiatjaf anyway you can overrule fiatjaf's fiat ruling on no-rich-text ;-)
Yeah, I think that much would be ok
