Delivery-Date: Mon, 14 Sep 2015 23:58:14 -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 E6B5F1E0BD1;
	Mon, 14 Sep 2015 23:58:12 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DB0A433418;
	Tue, 15 Sep 2015 03:58:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 74A4E33720
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 03:58:04 +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 oaH3wMJdvnF6 for <tor-talk@lists.torproject.org>;
 Tue, 15 Sep 2015 03:58:04 +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 4F90B33418
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 03:58:04 +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 352BCC31DA
 for <tor-talk@lists.torproject.org>; Mon, 14 Sep 2015 20:58:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1442289481; bh=qSYoD019Dlhpeu8cA7TOwQ+gz2t/fdwZKIwhLBjwgpQ=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=KViRghYwndy09EOYVM1GIi6cpb+DpWIq+UxPGfbNPIuTXSedipUK7ln7ZDaowY8gq
 +LYydJNr/lu4UhMcLrDT//zp8GdR2/MsaFojeWjOKv1fy/ShCHVjL9QtGmP4YZ259S
 BBl/MY5rTEwDlfM90F6dJTSARdaaWWt5269hGVSA=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: colinmahns) with ESMTPSA id 1BA761C01EA
Date: Mon, 14 Sep 2015 23:56:33 -0400
From: Colin Mahns <colinmahns@riseup.net>
To: tor-talk@lists.torproject.org
Message-ID: <20150915035631.GA17200@riseup.net>
References: <55F6100C.5030200@bitmessage.ch>
 <20150914011907.GA30016@riseup.net>
 <20150915032734.GL8355@torproject.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20150915032734.GL8355@torproject.org>
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>

* Mike Perry <mikeperry@torproject.org> [2015-09-14 20:27:34 -0700]:

>If you have Bitcoin, you can buy some SMS numbers for getting out of
>this lockout without giving up your real phone number:
>http://receivesmsonline.com/buynumbers
>
>That service also has free numbers available on their front page:
>http://receivesmsonline.com/, but those are likely to already be
>flagged/overused. Also, you might risk getting your account
>extra-special-locked by trying to use a free one that Twitter knows
>about.

Heh, did not know about these, bookmarking in case of emergency. For
what it's worth, I think Google Voice also used to give out a free phone
number for a while, but I can't remember if they are still doing this.
It's been a few years since I've used that service.

>> 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.
>
>Yeah, maybe. However, once a company starts down this path, it tends to
>become entrenched beyond all rational thought. I am not optimistic that
>Twitter will be any different.

I was thinking that someone might know the the equivalent of Alec
Muffet at Twitter. Someone who might be able help from the inside with
lobbying for Tor-tolerant or Tor-embracing policies at Twitter. Of
course this will still be a slow, uphill, and painful battle to try to
have someone listen...

>Welcome to the Nymwars 2.0!

You can pry my nyms from my cold dead hands Mike ;)
-- 
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

