A feed written in Markdown shows the Markdown as text, not formatted #284
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A feed whose items are written in Markdown, not HTML, shows the Markdown as it is:
**bold**,[a link](https://...),# headingsand- listsas raw characters, with its line breaks run together into one paragraph.Two ways a feed sends it:
<source:markdown>on an item, the item's text in Markdown. Scripting News sends it beside an HTML<description>; a feed could send it alone, which ipx ignores today, so the item shows no text at all.<description>(or Atom content, or JSON Feed'scontent_text) that is plain text with Markdown in it.Wanted: Markdown rendered to HTML, then cleaned by ammonia as any feed's HTML is. Where a feed sends HTML too, the HTML stays as it is.
Reference: Dave Winer, "The Web of Markdown", http://scripting.com/2026/10/06/005559.html
Done in
3a8d564, deployed in ipx and ipx-directory: a description with Markdown and no HTML tag is rendered to HTML (pulldown-cmark), and an item whose only text is source:markdown uses that. HTML is left alone, and plain text without Markdown stays as it was. ammonia cleans the result as any feed's HTML. Applies to items new from now on: the scanner does not rewrite an item it already has. Switching between HTML and Markdown when a feed sends both is #285.Correction: stored items are rewritten too, not only new ones. A scan compares each listed item with what is stored and writes again the ones the feed now tells differently (changed_items, #141), and an item whose Markdown description now renders as HTML differs, so it is rewritten on the feed's next whole read.