[451] Follow-up HTTP Status Code 451

[Niels ten Oever]

Hi Alp,

Thanks for this. It would be great to read more about the investigative work. Do you think if large providers would serve 451 when they are legally forced to do so, would worsen the current situation?

This is an initial campaign briefing I drafted during the hackathon:

https://github.com/451hackathon/451-imp-report/blob/master/1pager.mdown

Would be great to hear your comments!

Best,

Niels



On Fri, Aug 18, 2017 at 02:36:15PM +0300, Alp Toker wrote:
> 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.
> 




-- 

Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint	   2458 0B70 5C4A FD8A 9488  
                   643A 0ED8 3F3A 468A C8B3

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ghserv.net/pipermail/statuscode451/attachments/20170820/4f8a0191/attachment.sig>