HTTP Status Code for Legally-restricted Resources

Re:HTTP Status Code for Legally-restricted Resources by cagenut on Tuesday June 12, 2012 @09:17AM (#4100260)

This can't be a coincidence right? Its a way of saying that DMCA/lawsuit takedowns are digital book burning.

[ Parent | on HN ]

Re:HTTP Status Code for Legally-restricted Resources by pavel_lishin on Tuesday June 12, 2012 @10:45AM (#4100675)

Except there are plenty of legitimate DMCA takedowns.

[ Parent | on HN ]

Re:HTTP Status Code for Legally-restricted Resources by jlgreco on Tuesday June 12, 2012 @11:30AM (#4100930)

A 451 could be used in a lot more cases than just DMCA takedown'd documents.

[ Parent | on HN ]

Re:HTTP Status Code for Legally-restricted Resources by byoung2 on Tuesday June 12, 2012 @08:51PM (#4103744)

For example, court-mandated gag orders, nondisclosure agreements, national security, etc.

[ Parent | on HN ]

Re:HTTP Status Code for Legally-restricted Resources by gue5t on Tuesday June 12, 2012 @01:04PM (#4101451)

There have been plenty of "legitimate" book burnings.

[ Parent | on HN ]

Re:HTTP Status Code for Legally-restricted Resources by ktizo on Tuesday June 12, 2012 @03:54PM (#4102446)

Destruction of 'counterfeit' media. Because after all, just because you have a vast zero-scale network on which to distributively backup the collected artistic works of society in real time, doesn't mean you should, obviously. I mean, that would amount to the most complete open library of knowledge ever created in history, which would make so many existing business models obsolete that we just can't justify doing it, for the sake of the economy, cos y'know, money works, right?

[ Parent | on HN ]