Unfortunately they are not rendered as footnotes when printed
This seems like a fault in the printing process.
If the author is optimizing for one reading format, and you want to convert it to another, and it’s unsatisfactory in the new format, then perhaps the conversion process is what should be improved.
Good point. I experimented for ten minutes with saving the HTML, changing it and loading it again in the browser. But it doesn’t work for LessWrong. The article appears briefly and then it switches to: ‘Sorry, we couldn’t find what you were looking for.’ I didn’t feel like figuring this out.
This seems like a fault in the printing process.
If the author is optimizing for one reading format, and you want to convert it to another, and it’s unsatisfactory in the new format, then perhaps the conversion process is what should be improved.
Good point. I experimented for ten minutes with saving the HTML, changing it and loading it again in the browser. But it doesn’t work for LessWrong. The article appears briefly and then it switches to: ‘Sorry, we couldn’t find what you were looking for.’ I didn’t feel like figuring this out.
Try getting the article from greater wrong instead.
Good idea! I will try that.
This is a bug in Vulcan, the framework we’re built on; https://github.com/LessWrong2/Lesswrong2/issues/638 . We’ll come up with a workaround at some point.
Thanks for the info! By the way, Markdown included the period after ‘638’ in the
hrefattribute. Also a bug?