[toomim]

Here are three use-cases:

1. You are editing documents locally on your computer. This lets you double-click to view nice markdown in a web browser with a `file://` url.

2. You are editing a website, but don't have control over the server-side code.

3. You don't want to install a markdown rendering library on the server.

[majewsky]

> You are editing a website, but don't have control over the server-side code.

You don't have control over the server-side code, but it will let you inject <script> tags into the content? That seems a bit weird.

[slimsag]

GitHub pages is literally like this, no?

[majewsky]

You're right, though GHP is a bad example since it includes a Markdown renderer.