Live data from Hacker News

A New HTTP Status Code for Legally-restricted Resources

tools.ietf.org

1–9 of 9 posts

Re: A New HTTP Status Code for Legally-restricted Resources

#2
this is a prime example of a maliciously edited title. it shows as "Error Code 451: an HTTP error for censorship" at the moment which is what brsata submitted I guess.

the actual title of the draft is " A New HTTP Status Code for Legally-restricted Resources".

there can be many reasons, most prominently oldschool broadcasting licenses, that do not allow for global distribution. those have nothing to do with censorship.

Re: A New HTTP Status Code for Legally-restricted Resources

#3
post #2

this is a prime example of a maliciously edited title. it shows as "Error Code 451: an HTTP error for censorship" at the moment which is what brsata submitted I guess. the actual title of the draft is " A New HTTP Status Code for Legally-restricted Resources". there can be many reasons, most prominently oldschool broadcasting licenses, that do not allow for global distribution. those have nothing to do with censorshi…

Not maliciously edited but you are right. I've edited title to "A New HTTP Status Code for Legally-restricted Resources", the original title. "Error Code 451: an HTTP error for censorship" is from boingboing.net: http://boingboing.net/2012/06/13/error-code-451-an-http-erro...

Re: A New HTTP Status Code for Legally-restricted Resources

#4
post #2

this is a prime example of a maliciously edited title. it shows as "Error Code 451: an HTTP error for censorship" at the moment which is what brsata submitted I guess. the actual title of the draft is " A New HTTP Status Code for Legally-restricted Resources". there can be many reasons, most prominently oldschool broadcasting licenses, that do not allow for global distribution. those have nothing to do with censorshi…

Good point. That would definitely be a good use for this code, and the real title is more politically correct. In the poster's defense, though, the tone of the document really does seem biased toward government censorship activities.

Re: A New HTTP Status Code for Legally-restricted Resources

#6
post #2

this is a prime example of a maliciously edited title. it shows as "Error Code 451: an HTTP error for censorship" at the moment which is what brsata submitted I guess. the actual title of the draft is " A New HTTP Status Code for Legally-restricted Resources". there can be many reasons, most prominently oldschool broadcasting licenses, that do not allow for global distribution. those have nothing to do with censorshi…

As a side note to this, the author of the draft aknowledges a blog post Terrence Eden which do call for the creation of a HTTP code for censorship

Link: http://shkspr.mobi/blog/index.php/2012/06/there-is-no-http-c...

Re: A New HTTP Status Code for Legally-restricted Resources

#8
post #3
post #2

this is a prime example of a maliciously edited title. it shows as "Error Code 451: an HTTP error for censorship" at the moment which is what brsata submitted I guess. the actual title of the draft is " A New HTTP Status Code for Legally-restricted Resources". there can be many reasons, most prominently oldschool broadcasting licenses, that do not allow for global distribution. those have nothing to do with censorshi…

Not maliciously edited but you are right. I've edited title to "A New HTTP Status Code for Legally-restricted Resources", the original title. "Error Code 451: an HTTP error for censorship" is from boingboing.net: http://boingboing.net/2012/06/13/error-code-451-an-http-erro...

"Maliciously" was a word too strong, sorry.