[451] Follow-up HTTP Status Code 451
Alp Toker
alp at netblocks.org
Fri Aug 18 13:36:15 CEST 2017
It's worth noting that investigative work so far doesn't favor broader
451 adoption, indeed our findings suggest that it shifts the burden of
responsibility of self-censorship to content producers and hitherto
neutral intermediaries.
Data from our initial exploration of 451 use with Olga Khrustaleva in
Turkey and Russia during and after IETF 99 shows that 451 isn't yet
conclusive, but does indicate that use of the status code in the wild is
inconsistent with government takedown requests and official filtering
directives.
Glad to shift conversation to the list.
On 18/08/2017 12:36, Niels ten Oever wrote:
> and it might be nice if it would all come together in a
>
> 4. Campaign for adoption of HTTP Status Code 451.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ghserv.net/pipermail/statuscode451/attachments/20170818/def8f18c/attachment.sig>
More information about the StatusCode451
mailing list