Re:The 451 status code is now supported
by charonn0 on Friday March 18, 2016 @01:18PM
(#11313288)
I don't think it legitimizes censorship. Rather, it makes censorship obvious and unmistakable. A generic status code (like 403) is indistinguishable from a technical error and obfuscates the existence of censorship.
[ Parent
| on HN ]
Re:The 451 status code is now supported
by jsprogrammer on Friday March 18, 2016 @02:31PM
(#11313817)
A devious censor probably would not explicitly call out their censorship with a standard HTTP code.
It seems undeniable that this "feature" codifies censorship, making it more "acceptable".
"Oh, well they used the right code anyway"
back to approved activities
IIRC, the general rationale behind the 451 RFC was that this provides a means for a third party to communicate that they are censoring the content, presumably begrudgingly.
So, in the case at hand, GitHub is using 451 to communicate that a government censor has required that they take some content down, not that the company itself has decided to remove the data of its own volition.