Delivery-Date: Wed, 21 Jan 2015 15:04:24 -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=-4.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,URIBL_BLOCKED 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 11BB01E0C83
	for <archiver@seul.org>; Wed, 21 Jan 2015 15:04:23 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1B89C339E0;
	Wed, 21 Jan 2015 20:04:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4044B339D9
 for <tor-talk@lists.torproject.org>; Wed, 21 Jan 2015 20:04:16 +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 rYXaWlg67wvo for <tor-talk@lists.torproject.org>;
 Wed, 21 Jan 2015 20:04:16 +0000 (UTC)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by eugeni.torproject.org (Postfix) with ESMTP id 0D5A7339D6
 for <tor-talk@lists.torproject.org>; Wed, 21 Jan 2015 20:04:15 +0000 (UTC)
Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net
 [50.184.63.128]) (authenticated bits=0)
 by shell1.rawbw.com (8.14.9/8.14.9) with ESMTP id t0LK4CBe060505
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <tor-talk@lists.torproject.org>; Wed, 21 Jan 2015 12:04:13 -0800 (PST)
 (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be
 yuri.doctorlan.com
Message-ID: <54C0063B.2080504@rawbw.com>
Date: Wed, 21 Jan 2015 12:04:11 -0800
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <54BEB7AB.7090401@umail.iu.edu>
 <20150120202427.GB30692@moria.seul.org> <54BFA3F2.9030706@gmail.com>
In-Reply-To: <54BFA3F2.9030706@gmail.com>
Subject: Re: [tor-talk] Yelp blocking Tor users from viewing entire site
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 01/21/2015 05:04, Aymeric Vitte wrote:
> If they cannot detect a crawler using Tor, then they cannot detect any 
> other crawler, like a crawler switching IPs as mentionned in another 
> post, using vpns or proxies, etc
>
> So in that case it's useless to block Tor, because Tor network's size 
> is not really significant compared to other means that crawlers have, 
> probably they just choosed the easy way as well as crawlers might have 
> chosen the easy way too (use Tor), blocking Tor so they have solved 
> one problem.
>
> But in fact they have solved nothing if they are not protected against 
> crawlers, and if they are protected the protection would be something 
> like blocking the IP or sending a captcha. 

One other thing they try to protect from is people writing reviews for 
their own businesses. If someone logs into Yelp as the business owner 
and as a reviewer from the same IP, they would make such review "not 
recommended" (previously they made it "hidden" and protected with 
captcha). And possibly flag the whole business as suspect for writing 
false reviews. Yelp also sends businesses monthly reports on how many 
people viewed their Yelp listings and from which geographic areas. Tor 
defeats such detection schemes, therefore they decided to block it to 
simplify their guessing and reporting work.

Yuri
-- 
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

