suggested new markup option
"safe" - quot, amp, apos, lt, gt are explicitly escaped XML style
( " & ' < >) , and perhaps other non-ASCII characters get the usual treatment (so a
♥ ). this would be an "anti markup" of sorts, striving to be even more friendly for enabling more clever uses of activitypub/litepub. maybe a \r\n (0x0D, 0x0A) or \r or \n becomes a
This may be used as a similar style to
<code> in HTML; it should be meant to signal to human readers that the message is explicitly meant to be used by scripts / robots (and not necessarily for humans). Yes of course, clients should still escape the data here and not trust a remote server to properly escape this "escaped text", but presumably a local Pleroma instance could trust itself to escape its own content properly.
It's just like how popular webmail and desktop email clients have the "plaintext" formatting option that wraps text at 72 columns, includes the familiar
> way of quoting text, etc, meant to contrast the wild west of "default" -- markup usually means making the input
Alternative name to safe, "raw" , or splitting it between "rawtext" and "rawhtml" (complimenting "text" and "html" in the ATOM standard). Rawtext represents unformatted text with characters represented HTML entities whereas rawhtml represents a restricted HTML format with
< > " etc escaped
doing this helps normalize the idea that not all notes are meant to be blog posts or tweets.