Delivery-Date: Sat, 08 Nov 2014 14:00:37 -0500
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=-3.2 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_RHS_DOB 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 BC13F1E0B06;
	Sat,  8 Nov 2014 14:00:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 86D4331899;
	Sat,  8 Nov 2014 19:00:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B94863181F
 for <tor-talk@lists.torproject.org>; Sat,  8 Nov 2014 19:00:29 +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 E1oKuqlC7td3 for <tor-talk@lists.torproject.org>;
 Sat,  8 Nov 2014 19:00:29 +0000 (UTC)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com
 [IPv6:2a00:1450:4010:c04::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 5CAF131391
 for <tor-talk@lists.torproject.org>; Sat,  8 Nov 2014 19:00:29 +0000 (UTC)
Received: by mail-lb0-f173.google.com with SMTP id n15so4179056lbi.32
 for <tor-talk@lists.torproject.org>; Sat, 08 Nov 2014 11:00:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=H19vRIK/CGqThXwZAX/3KrD9bUq4EvNqKwCSOlIiKYc=;
 b=K668waNBh9HpwqfGeXFzGa2fdxoOW33n9Sq4vbub45lCElYhWg6evwKuBseRJinn19
 zY3+B8t7t7SLYt6XyZ5ackot5gI2mT42yljTKfZktCV5pFRVohRriHIHGRfSDNSQDhIL
 f+oRrJgljgAhopfflVaMGNSogMnJI78/oOZV5diLGHJZgHEtST8e9SSpCL9cDu/NxjZe
 BulQKACCaZWfplnr0B8a0/o8zXz47M4ZhGHhkZGk/Xt/sGOMDQE8sxJjOKSMNOGkZTax
 qaiJgwGrVvD5YyRgynxQISKDwD8NdvTM9IU434glCQLY1GSDIOWQVraJd+Avqf6WpSPo
 MTqg==
MIME-Version: 1.0
X-Received: by 10.152.43.197 with SMTP id y5mr4304945lal.82.1415473225868;
 Sat, 08 Nov 2014 11:00:25 -0800 (PST)
Received: by 10.112.234.197 with HTTP; Sat, 8 Nov 2014 11:00:25 -0800 (PST)
In-Reply-To: <20141108154414.D9FD720B55@smtp.hushmail.com>
References: <20141107155013.05aef6b2@meilong>
 <CAJ5w9HXkz6bbNuqy+K9B13EqJnQ57WD7XNxX_EhogMku95gxPg@mail.gmail.com>
 <20141108154414.D9FD720B55@smtp.hushmail.com>
Date: Sat, 8 Nov 2014 14:00:25 -0500
Message-ID: <CAJ5w9HVkXs+c1tNhAqt5M3oLWrFD0aE0kqDfmZOJMEo9e19q=g@mail.gmail.com>
From: Soul Plane <soulplane11@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] So much for using ixquick and Startpage: Now broken
	w/Tor
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>

On Sat, Nov 8, 2014 at 10:44 AM, l.m <ter.one.leeboi@hush.com> wrote:

> It's not broken. They explain clearly that the concurrent use of
> ixquick/startpage by multiple Tor users at a given exit relay can
> trigger automated abuse blocking. They're right. It could be abuse.
> The same reason Google does it. Why is this a surprise? The problem
> with Google is the connection sometimes 'spills' over to new circuits
> which puts you into an infinite loop of entering captchas. This makes
> Google just block some exit relays entirely for a time because of
> repeated failed captchas. Google really wants to make money so if they
> set a cookie for one of your circuits, and ask for a captcha, which
> then 'spills' to a new circuit, and you just choose a new
> identity--well it shouldn't be a surprise they decide to block a bunch
> exits for lost revenue. Just try your search on startpage/ixquick with
> a new identity.
>

Thanks, I know I can do that but I don't want to do that. Their help page
says  "Both Ixquick and StartPage are compatible with Tor, although use of
VPNs and Proxy services (including Tor) may occasionally trigger our
anti-abuse mechanisms. If so, you will temporarily be presented with a
small warning message, or a request to complete a CAPTCHA before continuing
with your search." [1]

I didn't get captchas and the warning didn't go away. So it seems broken.
It's a block unless you change identities until you get one that works. If
you have to repeatedly change identities doesn't that do something to
lessen anonymity?

[1]:
https://support.startpage.com/index.php?/en/Knowledgebase/Article/View/288/0/how-does-startpage-interact-with-tor
-- 
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

