Skip to content

Instantly share code, notes, and snippets.

@nikclayton
Created April 30, 2026 21:53
Show Gist options
  • Select an option

  • Save nikclayton/f1608fa674387e4dcf20b7419fa5ccf8 to your computer and use it in GitHub Desktop.

Select an option

Save nikclayton/f1608fa674387e4dcf20b7419fa5ccf8 to your computer and use it in GitHub Desktop.

It is, but it's a bit confusing. There's a couple of different things at play here:

First, mastodon.rxbrad.com reports it is running mastodon+glitch. So I expect you're using its feature that lets you write Markdown when you post.

Your server then converts that Markdown to HTML and sends the HTML on to the rest of the network. So Pachli doesn't see the backtick characters you used, it sees <pre> and <code> elements.

I.e., you're writing something like this:

This is some `code`.

and your server is sending

<p>This is some <code>code</code></p>

and not

<p>This is some `code`</p>

Second, I think you have the "Render Markdown" Lab preference enabled in Pachli. This works by trying to convert the incoming HTML back to a hybrid of HTML and Markdown1 and then passing it through a Markdown renderer.

But! Your server isn't sending HTML-that-contains-Markdown, it's sending Markdown-already-converted-to-HTML.

In theory this should still work, as the Markdown renderer ("markwon") also understands a subset of HTML elements, described at https://noties.io/Markwon/docs/v4/html/#predefined-taghandlers.

But! pre and code are not in this list. So the Markdown renderer ignores them, and you see them unformatted.

That last bit's a Pachli bug I can fix.

Footnotes

  1. For example, if you had posted This is some `code`. as "plain text" (per https://glitch-soc.github.io/docs/features/rich-text/, the "Authoring formatted toots" section) then that would arrive as <p>This is some `code`.</p>, the Pachli Markdown pipeline converts that back to This is some `code`., and then it's displayed.

@rxbrad

rxbrad commented Apr 30, 2026

Copy link
Copy Markdown

Gotcha. Thanks for the explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment