Delivery-Date: Tue, 15 Sep 2015 06:29:18 -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 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 B28AE1E0C9B;
	Tue, 15 Sep 2015 06:29:16 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id CE41435957;
	Tue, 15 Sep 2015 10:29:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 30CF734F27
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 10:29:08 +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 gDi4oBCS0fHC for <tor-talk@lists.torproject.org>;
 Tue, 15 Sep 2015 10:29:08 +0000 (UTC)
Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id BDAF630676
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 10:29:06 +0000 (UTC)
dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail;
 c=relaxed/relaxed; q=dns/txt;
 h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References;
 bh=jOJmvQ5nyi5UghJtIgSXiFEnPZV0wBW5CsDcVzzLTKg=;
 b=Uj2Yb2HcG871e9nETDa48F3RFhDF/6Xw7QPHGGzxyXEQZBmXkN+nGftG48uz8Do7SUwo19ZXUSAgHbUy/x7FXkvaRU1PTslFm9C3/p88dJQ4nbn/t+KzSUTTBRbQ83aaNVnipDFNRWjtbAg67ItBFA2WgbuWlf2j8qxq1n1ibMw=
Received: from 127.0.0.1 (BITMESSAGE [127.0.0.1])
 by mail.bitmessage.ch with ESMTPSA
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128)
 ; Tue, 15 Sep 2015 12:28:43 +0200
Message-ID: <55F7F2E2.6040902@bitmessage.ch>
Date: Tue, 15 Sep 2015 10:28:50 +0000
From: Tempest <tempest@bitmessage.ch>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <55F6100C.5030200@bitmessage.ch>
 <20150914011907.GA30016@riseup.net> <20150915032734.GL8355@torproject.org>
In-Reply-To: <20150915032734.GL8355@torproject.org>
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>

Mike Perry:
> 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

there's a number of tricks one can use to get around an sms/voice
requirement. i'm not particularly concerned for myself in that regard.
however, for people who simply need tor to safely use twitter, and
aren't quite as technologically savvy to use something like btc or other
options, this appears to be a problem that is continuing to grow. my
account was eventually unlocked due to support responding.  however,
within the past 30 days, another lock out received no responses at all
from support, which resulted in 2 weeks worth of down time. they simply
ignored me.

> 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.
> 
> Welcome to the Nymwars 2.0!

i agree. but it's worth a try.

-- 
gpg key - 0x2A49578A7291BB34
fingerprint - 63C4 E106 AC6A 5F2F DDB2 3840 2A49 578A 7291 BB34

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

