I like the spirit of text-only but Markdown is similar enough and gives clickable links, embeddable static images etc. Its the JS, CSS, video, audio and surveillance shenanigans which have gotten out of hand and become noisey (and nosey.)
I've been considering implementing a feature like this in my blog, but in a slightly more HTTP-ish way. Something like, if the Accept header leads with text/markdown, reply with markdown.
This feels more "pure" to me, but it also means that you couldn't actually use it from a typical web browser. So it'd be utterly pointless, but then again, so is my blog.
sounds like a net win. Markdown is a superset of plain text anyway. You could make Markdown the "source" format for each page and then the web server decides at last second which MIME type header to return based on requested suffix. But even if they request .txt the page body could be identical to the
md
I have a few WIP books where Markdown is my source format for similar reasons. I then use pandoc to render to txt, html, pdf, doc or epub as desired.
