Delivery-Date: Sun, 13 Sep 2015 21:20:48 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	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 809E91E088A;
	Sun, 13 Sep 2015 21:20:46 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3EC983543E;
	Mon, 14 Sep 2015 01:20:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C6F5C3543D
 for <tor-talk@lists.torproject.org>; Mon, 14 Sep 2015 01:20:37 +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 JCsHdIsf0FQ1 for <tor-talk@lists.torproject.org>;
 Mon, 14 Sep 2015 01:20:37 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id A316D31E2A
 for <tor-talk@lists.torproject.org>; Mon, 14 Sep 2015 01:20:34 +0000 (UTC)
Received: from cotinga.riseup.net (unknown [10.0.1.161])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 68B36C2A7F
 for <tor-talk@lists.torproject.org>; Sun, 13 Sep 2015 18:20:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1442193631; bh=7WBy0PWGAAuBttrOYZCrdIOVpjC+im9jTPKq5LmN9I4=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=J+bu88H0dCshpkMdinqEGHT+hOUydo4y7dWJTrV4+3CwFCZg1KQqLO3d4ORGDcbgj
 UORRwuXH1j6XFNknEAR5/Ck6adF6f2Kc/OzbhnMrNs5Lct1qwSCjAiN7bPOB6vYW4a
 WLurMtIXOdqSvgLe3YlVNhvr5Qis0CJrn0nwZgZk=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: colinmahns) with ESMTPSA id 6E92A1C033E
Date: Sun, 13 Sep 2015 21:19:09 -0400
From: Colin Mahns <colinmahns@riseup.net>
To: tor-talk@lists.torproject.org
Message-ID: <20150914011907.GA30016@riseup.net>
References: <55F6100C.5030200@bitmessage.ch>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <55F6100C.5030200@bitmessage.ch>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
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-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>

* 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. 

Does anyone on this list has contacts in Twitter who might be open to
talking with the community, can you ask them to join this list? I really
would love to see this issue resolved along with my account not being
locked out. 

[0]: http://techcrunch.com/2015/03/02/twitter-tor-phone-verification/
[1]: https://twitter.com/search?q=%23twittertorlockout 
-- 
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

