Delivery-Date: Wed, 02 Dec 2015 20:36:46 -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=-1.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,TVD_PH_BODY_ACCOUNTS_PRE,
	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 32F551E0CE4;
	Wed,  2 Dec 2015 20:36:45 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6CFC936DCE;
	Thu,  3 Dec 2015 01:36:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1B3C036B29
 for <tor-talk@lists.torproject.org>; Thu,  3 Dec 2015 01:36:35 +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 xNH2Jcm7GWFc for <tor-talk@lists.torproject.org>;
 Thu,  3 Dec 2015 01:36:35 +0000 (UTC)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com
 [IPv6:2a00:1450:4010:c07::236])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id B612735ADF
 for <tor-talk@lists.torproject.org>; Thu,  3 Dec 2015 01:36:34 +0000 (UTC)
Received: by lfs39 with SMTP id 39so70279705lfs.3
 for <tor-talk@lists.torproject.org>; Wed, 02 Dec 2015 17:36:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=17oYRy6x1uNnG/F61enOZmjly5OMJUS8oy1cxFcb4/U=;
 b=Ye+4ej1ftZNPLI7JrahtxeTvLLtOKKe3dbYah5b3juXjLSVrG5XWOtMg/CpbhAqwl1
 fs+HfA7fO9pH7aR8X1kPTIL0hZjmfDxqJ7MQHrasmCXuCPKDHXmRzZWLV9cp746I369P
 trOq1jXd4CzAINhzWEmU1ZqvgHpxi5C2PrW4yYhzvcBCiFNONd6B3IVuBqT7mRKnKipM
 pMezfFLdmAtC30QfuvHCL8tlbtTRJIZwCLoEeqohBoFWljC0W2F3wvcWgIVrH73yGE/K
 GssjeOcyvPVH4lpEjOnTh0WC4VCEpgMn2F9jFzWDNb6h/SQGEoufOApgY5RMv/aQ0erX
 fGtg==
MIME-Version: 1.0
X-Received: by 10.25.21.70 with SMTP id l67mr4031283lfi.27.1449106591614; Wed,
 02 Dec 2015 17:36:31 -0800 (PST)
Received: by 10.25.40.66 with HTTP; Wed, 2 Dec 2015 17:36:31 -0800 (PST)
In-Reply-To: <565D915B.3040904@bitmessage.ch>
References: <20151112133507.GA16219@inner.h.apk.li>
 <564710D6.6040606@riseup.net>
 <20151114120019.GG16219@inner.h.apk.li>
 <56472F3C.8080902@riseup.net> <565D915B.3040904@bitmessage.ch>
Date: Wed, 2 Dec 2015 17:36:31 -0800
Message-ID: <CAJVRA1TO1POmgneD3=wTamo-yGBNORc9xJcHbWSRsZLo61cCmQ@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk <tor-talk@lists.torproject.org>
Subject: Re: [tor-talk] twitter tor block redux
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 Tue, Dec 1, 2015 at 4:23 AM, Tempest <tempest@bitmessage.ch> wrote:
> i noticed a number of accounts were suspended due to using tor recently.
>  any news on the status of accounts locked out in the last round of
> twitter's tor censorship? i'm coming up on 96 hours since twitter has
> acknowledged in email that there was an "automated behavior" problem
> which resulted in the suspension of my account until i provide a phone
> number.

they seem to regularly attempt a "tie all accouns to secondary
identifiers" phase.



>  the last time twitter had taken this long to reply to my
> support ticket, it turned out they were simply ignoring my emails for
> some reason.

i dodged this lock-out having previously associated a hotspot puck SMS
with a Tor-only twitter account.

perhaps pre-paid is sufficiently tied-in to avoid the automated mechanisms...



> while i'm sympathetic to twitter in their attempts to combat spammers,
> their claims that they "fixed" the problem with the tor suspensions
> feels like empty pr at this point,

it was always, and will always be, total bullshit from Twitter.

question is if they get enough flak to cut the crap...


best regards,
-- 
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

