Outline is better from a moral standpoint and closer to say (but not quite) the internet archive.
While it's possible to do without storing anything on disk (strange requirement imo - but you can keep it in memory on the server if you really want), it's a lot more practical to do this work in the backend. And that's also what outline is doing:
outline's frontend will do an AJAX request to outline's servers to actually fetch the article from a blog and serve that back[1]. So they could do this easily without frontend javascript. But I think the UX would suffer on many levels. Having a frontend in javascript allows outline to do better caching, better user experience, etc. The only downside to using JS is that it doesn't work for people still in 1995 and for people who disable their javascript.
[1]: example fetch call: https://outlineapi.com/v3/get_article?id=6ps979
edit: fixed typos
Not at all. Outline doesn't essentially present the content as their own.
> 2018-12-20 nickmchardy.com
The difference is that the link in Saowen.com directs to https://www.saowen.com/source/site/nickmchardy_com, whereas the one on outline goes to the source.
https://www.saowen.com/a/3b4deadad676021a51cbcee5d5fc1ec4269...
I am vehemently against Saowen.com stealing content, but this is practically quite similar to how outline works (to remove css or bypass paywall), wonder why people (especially on HN) don't have issue with those:
https://outline.com/DnVGCw
https://www.outline.com/dmca.html
Edit: Replace "Not to defend the site" with "I am vehemently against Saowen.com stealing content"