| From the article: My suggested implementation is to institute site bans based on reports / awareness, and to leave those bans in effect until the problem can be verified to be fixed. That is: the system needn’t be perfect, but it should exist, bans should be instituted when requested, and sites themselves must take positive action to see them lifted. (Author) The point is to make noncompliance painful. If the main body content is feasibly viewable in a GUI and a console browser, that's sufficient. In the case prompting this request, I was able to successfully view the content with the additional steps of locating the Markdown source, and re-rendering that as HTML, via a pandoc pipeline: pandoc --standalone -f markdown -t html -o - \
https://raw.githubusercontent.com/anderspitman/anderspitman.net/master/entries/16/entry.md |
/usr/bin/w3m -T text/html
In 0.3s as it happens, for those concerend with efficiency measures.I wouldn't consider the process of that as sufficient, but the result certainly was. Collateral damage is unfortunate. Responsibility lies with the violator. |