> "we can't serve you this because your jurisdiction forbids it (but ours doesn't)" should almost never arise.
Uh, it happens all the time. In fact, it's by far the most frequent kind of censorship.
From TFA:
- https://en.wikipedia.org/wiki/Censorship_of_Facebook
- https://en.wikipedia.org/wiki/Censorship_by_Google
- https://en.wikipedia.org/wiki/Censorship_of_Twitter
Most major web services are based in a country with relatively lax censorship laws but still comply with censorship laws in other jurisdictions.
Re:Why 451?
by thescriptkiddie on Saturday December 19, 2015 @07:41PM
(#10765543)
While this happens all the time, I would argue that it is not a good use case for HTTP 451. A better approach would be to just serve the content. If a country wants to censor your content they can do it the hard way. Don't help the bad guys.
> I would argue that it is not a good use case for HTTP 451
What is a good use case for HTTP 451 then?
Rarely does the calculus favor getting your entire site blocked because you refuse to censor one piece of content. At least by serving HTTP 451 you could also potentially offer suggestions like using Tor.
Re:Why 451?
by paulddraper on Saturday December 19, 2015 @10:01PM
(#10765874)
If you don't play along, the bad guys will block your whole site.
"We can't serve you this because our jurisdiction forbids it" seems likely to arise more often.
That said, I also don't think the 4xx/5xx distinction matters as much here as the evocative implication of using 451 specifically.