In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. If anything, it says the opposite, it says it contains HTML. It’s therefore not unreasonable for other platforms to render it as such.

Actually, the name property is explicitly plain text, it shouldn't contain any type of markup, whether that be markdown or HTML.

Also, this gives me real text-on-image-in-Facebook-post-just-to-get-noticed vibes.

If everybody can use Markdown in their post titles, then everybody will use Markdown in their post titles, until it's a mess of colors, bold, and italics.

Markdown is plain text, so it's fine to go in the field. It's also fine for apps to allow OP's post to look like garbage because there's no requirement for support.

In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. …. it says it contains HTML

This seems like a bug. Regardless of what clients may support, the json ought to accurately describe fields

The Lemmy backend doesnt treat this field as markdown, if you look at the Activitypub data (curl -H "Accept: application/activity+json" https://lemmy.world/post/24241974 | jq) the title is federated as plaintext. Only lemmy-ui decides to render it as markdown for some reason.

Hmm, but the best part about markdown is that it is human readable regardless so it should still be fine

Nor Boost. It does in Raccoon, though.

or in Jerboa

Or Thunder

Do you also have the Android weirdness in which the tick marks appear to be in a different place? (Not Jerboa-specific)

ABSOLUTELY NOTHIN

I mean, code could work and maybe ^superscript^ or ~subscript~ and that's about it I think

Oh no indeed

Guess it depends on your client because it works for me.

What client do you use?