News for hackers. Stuff that matters.
Re:HTTP Status Code for Legally-restricted Resources by bashzor on Tuesday June 12, 2012 @09:13AM (#4100243)
Is this a troll or something?
Re:HTTP Status Code for Legally-restricted Resources by jaachan on Tuesday June 12, 2012 @09:34AM (#4100336)
There are situations where a resource is blocked, but transparently. For example, the pirate bay is blocked in some countries. However, it's done publicly, and that the site exists isn't denied. The ISPs that effect the blocking could use this status code to inform people who try to visit it that the site does exist, but they can't access it because the government says so. This could, in theory, divert activity towards the ISP (which has nothing to gain from implementing such blocks) to the government. That is, instead of spamming the ISP's helpdesk, they could petition their representatives.

Of course, in some situations the block is supposed to be also denying the existence of the site, and in such cases this status code wouldn't apply. That's mentioned in the RFC (section 4.1).

Re:HTTP Status Code for Legally-restricted Resources by sgift on Tuesday June 12, 2012 @09:22AM (#4100283)
Maybe, but if I have to guess differently than you think: They probably want to use this to "troll" governments and heavy users of DMCA take-down notices. These people usually don't like it if users notice that they were responsible, so this is against their interests.

Reminds me of this: http://news.ycombinator.com/item?id=4048828

Re:HTTP Status Code for Legally-restricted Resources by delinka on Tuesday June 12, 2012 @10:16AM (#4100508)
I think it's a fabulous idea. Request and item that been the subject of a takedown notice, receive the details of who produced the takedown.
Re:HTTP Status Code for Legally-restricted Resources by wmf on Tuesday June 12, 2012 @11:32AM (#4100939)
Google sort of does that, although you have to go to Chilling Effects and look up the takedown.