@reiver Also PieFed I believe, as a Lemmy-inspired and somewhat compatible software

@reiver Do they support inlining html in markdown as designed https://daringfireball.net/projects/markdown/syntax#html ?

@aslakr

That is a good question — but, I'm not sure.

@reiver

Mastodon Glitch Edition
https://glitch-soc.github.io/docs

@reiver Markdown or its subset is supported by almost every platform except Mastodon.
But PeerTube is the only software I know that puts markdown in content instead of HTML.

@reiver #WriteFreely uses Markdown by default too, but of course sends out HTML to the fediverse

@reiver@mastodon.social add in NodeBB as well. Markdown first, and probably HTML too, although it will probably be sanitized to death on the way out.

Speaking of handling markdown. I created funfedi.dev Media Types a while ago (and just added it to the navigation). I lost interest when I saw that nobody properly handled the mediaType attribute of a note. Not that I know what I expected.

Can you explain what goes on in mitra? When mediaType is text/markdown. It changes __bold__ to <p>__bold__</p>, otherwise no paragraph tags. I'm pretty sure, I was once told to use __ for bold and * for emphasize. So my markdown should be good.

Full example ... input activity -> mitra api response

Final note: I am not sure what I would want a proper data format to do. I find the solution of W3C ActivityPub (not W3C ActivityStreams) proposes of putting HTML in content and adding source with the original, from which the HTML was generated ok. Of course, this leaves the existence of the summary and name field superfluous.

@helge @reiver

>Can you explain what goes on in mitra?

When mediaType is text/markdown, the entire content is wrapped in a <p> tag. This was done for compatibility with PeerTube. I think <p> was needed to create a space between the title (name) and the content, since title is prepended to content in Mitra (also a compatibility hack -- for Mastodon API clients).

I think the wrapping in <p> is just plain good practice because otherwise rendered content could be injected somewhere resulting in invalid HTML.

Not that browsers ever reject bad HTML anyway heh</p>