You're interpretation is disingenuous. Yes, the larger story is about the decay of intellect in society. However, it's a forced conversion, so that's where the censorship comes into play.
The job now falls to the Writermen. They excerpt, rewrite & aggressively-SEO... so that no original, true, or subversive ideas ever rank in top 450 search results (unless wrapped in neutralizing snark).
This reminds me very much of the TCP Evil Bit [1]. That is, it seems like the issue of whether anybody would actually set this is essential to the question of whether or not it would work.
One could even imagine that governments would want people to live in ignorance of the existence of restrictions. It's 100% the Ethan Zuckerman Cute Cat Theory of Internet Censorship [2]. The government would rather that you have all of YouTube except the subversive content, because then you might not notice the restriction and so will learn not to care.
Indeed, from the document:
"The use of the 451 status code implies neither the
existence nor non-existence of the resource named in the
request. That is to say, it is possible that if the legal
demands were removed, a request for the resource still
might not succeed."
That suggests to me that the author is also aware of this problem.
It should be noted that Google has done an amazing job in trying to fix this problem by trying to force whole services to be blocked when that's feasible and by transparently explaining (in the UI itself!) when content is unavailable for legal reasons. Kudos to them.
For that reason, I would say such an effort is worthwhile even if it won't have much impact: it's quite likely that it will help further the norm that when censorship exists it should exist transparently. That's a cause worth fighting for, even if every step is going to be a huge challenge.
People will set this to indicate that they had to censor something. Obviously if you don't want the censorship to be detected, you will not use this code.
"This request may not be serviced in the Roman Province of Judea due to the Lex Julia Majestatis, which disallows access to resources hosted on servers deemed to be operated by the People's Front of Judea."
I think if these types of messages were as jarring as possible instead discreetly displayed in the existing interface it would heighten people's awareness of these issues.
There's no reason a site couldn't serve content along with the 451 code, just as HTTP200 is served with content.
In fact, that's a SHOULD in the RFC:
Responses using this status code SHOULD include an explanation, in
the response body, of the details of the legal demand: the party
making it, the applicable legislation or regulation, and what classes
of person and resource it applies to.
I have mixed feelings about that. On the one hand, you're right that people should be made distinctly aware when something is being censored. On the other hand, you have to be careful not to convey the sense that the user is in the wrong or frighten anyone into self-censorship by giving the impression that the user could be sold out to an oppressive regime by the service provider.
The 451 status code is optional; clients cannot rely upon its use.
It is possible that certain legal authorities may wish to avoid
transparency, and not only demand the restriction of access to
certain resources, but also avoid disclosing that the demand was
made.
It seems this clause, as highlighted by deepblueocean in his "TCP Evil Bit" comment, is what is most disturbing...
Shouldn't it be made mandatory? Can it be made mandatory?
The GFW generally works on the TCP layer, resetting the session which delivers some sensitive-keyword-containing payloads, both in and out of the boundary.
It appears they deliberately chose 451 in homage to the great Fahrenheit 451 (or more specifically, to the dystopian future presented in the book).[1]
[1] http://www.techdirt.com/articles/20120725/06093819827/truth-...