News for hackers. Stuff that matters.
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

Re:The 451 status code is now supported by pcl on Friday March 18, 2016 @03:13PM (#11314134)
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.

Re:The 451 status code is now supported by morninj on Friday March 18, 2016 @04:44PM (#11314836)
If you send a DMCA takedown notice, you don't get to choose the status code that gets displayed after the content is removed.