Delivery-Date: Tue, 15 Sep 2015 05:03:05 -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 10AA81E06F1;
	Tue, 15 Sep 2015 05:03:04 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 36DF835B4D;
	Tue, 15 Sep 2015 09:02:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 13BB435B8F
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 09:02:55 +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 0kxlKlJJo9Ix for <tor-talk@lists.torproject.org>;
 Tue, 15 Sep 2015 09:02:55 +0000 (UTC)
Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "m.saper.info", Issuer "Marcin Cieslak 2011" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id BE08B35AEA
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 09:02:54 +0000 (UTC)
Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::])
 by m.saper.info (8.14.9/8.14.9) with ESMTP id t8F92oqB041885
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 09:02:50 GMT
 (envelope-from saper@saper.info)
Received: from localhost (saper@localhost)
 by m.saper.info (8.14.9/8.14.9/Submit) with ESMTP id t8F92oQm041882
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 09:02:50 GMT
 (envelope-from saper@saper.info)
X-Authentication-Warning: m.saper.info: saper owned process doing -bs
Date: Tue, 15 Sep 2015 09:02:50 +0000
From: Marcin Cieslak <saper@saper.info>
To: tor-talk@lists.torproject.org
In-Reply-To: <20150915032734.GL8355@torproject.org>
Message-ID: <alpine.BSF.2.11.1509150902100.41605@z.fncre.vasb>
References: <55F6100C.5030200@bitmessage.ch>
 <20150914011907.GA30016@riseup.net> <20150915032734.GL8355@torproject.org>
MIME-Version: 1.0
Subject: Re: [tor-talk] tor + twitter issues
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 Mon, 14 Sep 2015, Mike Perry wrote:

> Colin Mahns:
> > * Tempest <tempest@bitmessage.ch> [2015-09-14 00:08:44 +0000]:
> > 
> > >to sum up, twitter now appears to be desiring phone numbers from tor
> > >users in order to use their service. without feedback, i expect this
> > >will get worse. over the past 30 days, twitter has regularly locked me
> > >out and required password resets. this is the first time i've been
> > >required to provide a phone number to get my account unlocked.
> > 
> > Sadly Twitter seems to have been enforcing this over the past year[0] or
> > so, and there doesn't seem to be an end in sight. IIRC, Twitter tries to
> > do this in an attempt to try and curtail perceived abuse and/or trolls
> > from using Twitter as a platform, but they go about it in the worst way
> > possible.
> > 
> > The hashtag #TwitterTorLockout[1] has been used by several members of
> > the community (including devs) to voice their complaints about Twitter
> > doing this, but as you can see nothing has improved.

I don't have a phone number behind my Twitter account and it just
asks me to confirm my email address.

Not perfect, but way better.

~Marcin
-- 
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

