Post #4187412

2026-07-29 07:27 UTC

I do see the formatting on your instance too, so it is probably voyager that's the culprit here. I assume it relies on the source field on posts for the formatting, which contains the post in Markdown. But that's a threadiverse feature, Mastodon doesn't support that. The actual intended way to federate formatting on the protocol is to send it as HTML and then the receiving server interprets the HTML. The actual projects like Piefed and Lemmy understand that the Markdown isn't universal and so fall back to interpreting the HTML when it's not present. So the post appears as intended there. But I guess apps might not be as thorough there and solely rely on the Markdown with no fallback. So when there is no Markdown, the formatting is lost to them. Just my thoughts on the matter though, haven't actually looked at the code.

Replies (1)

@kathsone@infosec.exchange 2026-07-29 07:35

@Pamasich@kbin.earth The mastodon used in my instance is an enhanced fork that allows me to write in Markdown. In the past, I've encountered some Lemmy apps that didn't compile the formatting correctly (for example, a hashtag at the beginning of a paragraph was interpreted as the # that defines the head, resulting in a paragraph written in huge letters). Another problem is the size of "header 1" compared to "header 7": since these tags were designed for typographic output, it's not possible to maintain a consistent difference between all seven "headers" on screen, otherwise you'll end up with a gigantic "header 1." A good compromise for developers is to focus only on the first two or three headers. @NetscapeNavigator@vivaldi.net @fediverse @iftas@mastodon.iftas.org @Zomg@piefed.world @Zomg@lemmy.world

Open ##4187580