Delivery-Date: Tue, 27 Jan 2015 20:54:03 -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 D50B21E0B49
	for <archiver@seul.org>; Tue, 27 Jan 2015 20:54:01 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8843A32B65;
	Wed, 28 Jan 2015 01:53:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 015D532A49
 for <tor-talk@lists.torproject.org>; Wed, 28 Jan 2015 01:53:53 +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 9cVyfWd-IKzl for <tor-talk@lists.torproject.org>;
 Wed, 28 Jan 2015 01:53:52 +0000 (UTC)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by eugeni.torproject.org (Postfix) with ESMTP id C9C04322C2
 for <tor-talk@lists.torproject.org>; Wed, 28 Jan 2015 01:53:52 +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 t0S1rn5e066072
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <tor-talk@lists.torproject.org>; Tue, 27 Jan 2015 17:53:49 -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: <54C8412C.1080409@rawbw.com>
Date: Tue, 27 Jan 2015 17:53:48 -0800
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.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>
 <54C0063B.2080504@rawbw.com> <20150127152845.3872c27f@meilong>
In-Reply-To: <20150127152845.3872c27f@meilong>
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: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 01/27/2015 06:28, =D6yvind Saether wrote:
> This is clearly not why they are blocking Tor. Yelp has decided that
> you can't read their website anonymously. If they were blocking http(s)
> POST requests then that would be another story. As someone who has a
> bunch of websites myself I do have some understanding as to why someone
> would block http(s) POST but simply denying people access to read your
> website anonymously is going way further.

Let's say user A wrote the review for business B few months ago, from =

their own networks. Now, they both log into Yelp (using only GET =

requests) from the same IP or net. This business, and possibly the =

reviewer too, will get flagged by Yelp, because Yelp will decide these =

two are likely related. Only because of GET requests from the same net. =

Yelp is very sensitive to this, because too many businesses ask =

customers to write reviews while they are still in the office, show them =

Yelp, ask to open an account, etc. Yelp wants to prevent such things, =

and wants to have access to "real" IPs for that. That is one of the =

reasons they ban tor. Banning only POST requests is what one would do =

when they try to be open about what they are doing. Yelp doesn't try to =

be open, and instead lets you leave the review, then watches people's =

activities and patterns, mines data, and then labels certain reviews as =

not recommended. They also don't hide reviews immediately, only after a =

week or so, when they figure you aren't looking any more. This is =

different philosophy, and much more subtle and secretive approach.

Otherwise, people can access it without login, without cookies, I tried =

few VPNs, it also works fine through them.

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

