It seems undeniable that this "feature" codifies censorship, making it more "acceptable".
"Oh, well they used the right code anyway"
back to approved activities
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.
edit. language + explanation.
Censorship (external legal request) exists and this is a fact. The mere engineering projection of it does not strengthen it. On the contrary, through the 451 status code we can know that you cannot have access due to an "external legal request".
Yes because I really wanted to see that thing. If I get 404 on something I want to see I will try through Tor and I will try with at least a few circuits. And if Tor gets through I then usually test with other networks just as I did with this.
I know that many people probably don't do that and you have a valid point with the masking but a better solution would be stopping censorship, not a new errorcode
But, we can enable Internet companies to better-expose when rights requests and censorship has been used to block information.
Before, all you'd get on GitHub (per the release) was a 403, which could have been any number of things and was, in any case, an obfuscation of why you couldn't access the resource. If a person doesn't see a reason to investigate, they'll just move on.
This gets us closer to conversations about censorship.
If I get a 451 error, I'll know it's censorship and can use something like Tor to get around it.
Actually, I'm sure there will be some browser extensions soon to automatically use a proxy if a 451 error is returned.
This status-code is a great solution to inform the public about it.
It's pretty much the go-to thing for anybody nefarious who wants to have something censored without all the trouble and blatant impossibility of having their claims vindicated in court.
Those obstacles could be censorship, or copyright infringement, or illegal mathematics - anything.
First time I saw it was in December and after that in January, both on the same site. The site that was blocked was archive.is.
This block was targeted at Finland and none of the different Internet connections I tried could get to the site, I tried my home connection, cellular and connecting from my school network. It's a shame that anyone even thought of censoring such an useful tool for history and other legitimate uses. I wrote a thing about it to a Finnish newspaper and a few weeks after that the block was gone. I suspect that the newspaper conatcted archive.is and it was removed so they don't get bad publicity.
It was kind of ironical that I had to subvert the archive.is censorship to read an archived version of a thread discussing web censorship in Sweden.
I think this error code is a bad idea as it legitimizes censorship.