@neil The glitch-soc version of Mastodon renders Markdown
Conversation
Notices
-
Embed this notice
Flippin' eck, Tucker! (losttourist@social.chatty.monster)'s status on Friday, 03-Mar-2023 22:42:49 JST Flippin' eck, Tucker! -
Embed this notice
clacke (clacke@libranet.de)'s status on Friday, 03-Mar-2023 22:42:44 JST clacke @loke @losttourist @neil There is an additional field in the standard to optionally retain the source code, but nobody uses it.
www.w3.org/TR/activitypub/#sou… -
Embed this notice
Elias Mårtenson (loke@functional.cafe)'s status on Friday, 03-Mar-2023 22:42:45 JST Elias Mårtenson @losttourist @neil The content is presented in HTML form though. The markdown isn't visible to the client. That's how I understand it.
In conversation permalink -
Embed this notice
Flippin' eck, Tucker! (losttourist@social.chatty.monster)'s status on Friday, 03-Mar-2023 22:42:46 JST Flippin' eck, Tucker! @loke @neil I think the key point is that the client needs to understand the text/markdown MIME type, otherwise even if markdown text is used in a post it doesn't get formatted
In conversation permalink -
Embed this notice
Elias Mårtenson (loke@functional.cafe)'s status on Friday, 03-Mar-2023 22:42:47 JST Elias Mårtenson @losttourist @neil and this is the same post rendered in Tusky.
In conversation permalink Attachments
-
Embed this notice
Flippin' eck, Tucker! (losttourist@social.chatty.monster)'s status on Friday, 03-Mar-2023 22:42:48 JST Flippin' eck, Tucker! @neil i.e. the above post looks like this:
In conversation permalink Attachments
-
Embed this notice
Bob Jonkman (bobjonkman@mastodon.sdf.org)'s status on Sunday, 05-Mar-2023 11:56:34 JST Bob Jonkman ActivityPub's "source" element comes close to e-mail's "Content-Type: multipart/alternative"
I wonder why ActivityPub didn't re-use e-mail's Content-Type structure. Maybe Christine can comment? @cwebber
In conversation permalink clacke likes this.
-
Embed this notice