3 ms·
I agree 90% with this; .txt files get most of the job done! ;-) The other 10% where i don't fully agree comprises of hyperlinks; i need me some clickable hype
by mxuribe 10y ago
I agree 90% with this; .txt files get most of the job done! ;-) The other 10% where i don't fully agree comprises of hyperlinks; i need me some clickable hyperlinks. :-)
- walterbell 10y agoBrowser option to make hyperlinks clickable when rendering text files? Or client-side browser rendering of text-based markdown.
- happyslobro 10y agoHaving browsers intelligently render `text/markdown` sounds like a great idea. And while we're waiting on the browser implementation, maybe we can find some sort of temporary workaround to send a markdown parser to the client?
- pfooti 10y agoAs long as I can make text blink, I'm happy.
- Pete_D 10y agoMaybe we could just send the raw markdown anyway - it might not be pretty on all clients, but it should be _legible_ on all clients. Or maybe we could send markdown if the user agent included text/markdown in the request's Accept header, and pipe it through a markdown->HTML filter otherwise. I would love to see some kind of native markdown support on the web.
- walterbell 10y agoA web search turned up this Firefox plugin, https://addons.mozilla.org/en-US/firefox/addon/markdown-viewer/ https://addons.mozilla.org/en-US/firefox/addon/markdown-view..., are there other good ones?
- krisdol 10y agoNo, hyperlinks failed us. It's all about single-page apps. Put all of your content and all of the content you would have linked to in your .txt. We need someone to build Reactxt.