Delivery-Date: Sat, 03 Oct 2015 08:07:25 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id ED81D1E0677;
	Sat,  3 Oct 2015 08:07:23 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B865E37FE6;
	Sat,  3 Oct 2015 12:07:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AEA7837FE2
 for <tor-talk@lists.torproject.org>; Sat,  3 Oct 2015 12:07:12 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id JhwYFZ2m5M1F for <tor-talk@lists.torproject.org>;
 Sat,  3 Oct 2015 12:07:12 +0000 (UTC)
Received: from phil.hr3.wk3.org (hr3.wk3.org [178.63.16.10])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 787F337FCD
 for <tor-talk@lists.torproject.org>; Sat,  3 Oct 2015 12:07:12 +0000 (UTC)
MIME-Version: 1.0
From: malte@wk3.org
To: tor-talk@lists.torproject.org
References: <CADop2NG232W9WKdu4azvr5kncqaGF5KRmd60Frq3K7JE3rkEsg@mail.gmail.com>
In-Reply-To: <CADop2NG232W9WKdu4azvr5kncqaGF5KRmd60Frq3K7JE3rkEsg@mail.gmail.com>
Message-ID: <20151003120704.23837.29320@solidarity.enteig.net>
Date: Sat, 03 Oct 2015 14:07:04 +0200
Subject: Re: [tor-talk] Accessing Cloudflare sites on TBB
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Quoting Virgil Griffith (2015-10-03 01:40:22)
> Presuming they are
> unwilling to completely drop the captcha, what would be a step in the right
> direction?

I would add to the list, that offering read-only access would be nice.
So just delivering the cached content instead of the captcha, would be a
very easy solution in that direction.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

