Delivery-Date: Wed, 05 Nov 2014 14:33:49 -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=-4.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 112D31E06F1;
	Wed,  5 Nov 2014 14:33:47 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 33AAF31A1A;
	Wed,  5 Nov 2014 19:20:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3BCA131A10
 for <tor-talk@lists.torproject.org>; Wed,  5 Nov 2014 19:20:33 +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 5fymaqI799Ut for <tor-talk@lists.torproject.org>;
 Wed,  5 Nov 2014 19:20:33 +0000 (UTC)
Received: from mail-qc0-f169.google.com (mail-qc0-f169.google.com
 [209.85.216.169])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 1BC2D319EF
 for <tor-talk@lists.torproject.org>; Wed,  5 Nov 2014 19:20:30 +0000 (UTC)
Received: by mail-qc0-f169.google.com with SMTP id i17so1153754qcy.14
 for <tor-talk@lists.torproject.org>; Wed, 05 Nov 2014 11:20:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=5N6w0t08+111oFd0/v/HOV59AyA++tGABj0tPanNnhc=;
 b=isqITuNdVMROt4H9KfOT/DxjCg9tBGmz27mRMlZ73pxyqnCMTQfyqoaB64Dj/Pzltv
 jEo0AblbeGvkL7eLrC/hsjkIzGU7w9PPXSCovGlqomPjdBs9AEwhxYdKQ7rbhgmIE92v
 AvoTgsYkvmjDGDmVYFJSKO0CfCtCEV9ptRR43Q4we2CYV1y4ZRxjffprzZTy72UQpjxl
 UP7iQ34hrPDdNRSclKhOPBIuvmI3DYZKJRWMYlI09+V+iV5T1sgCDkjxRDrWp2a8WLKE
 j2V6JQhLgehLogaKit7b4LeTu05nE33N1byCHus41Iuzt2ReqOVFgGcGKyCCl+kJLbh7
 tjgw==
X-Gm-Message-State: ALoCoQnsfq0yob+Teyt0RdxMXJAaku9kd486evNwvIlJxZGddYMwihZrrkfJk8oztcotX1Wer30N
MIME-Version: 1.0
X-Received: by 10.140.88.100 with SMTP id s91mr52665934qgd.65.1415215227481;
 Wed, 05 Nov 2014 11:20:27 -0800 (PST)
Received: by 10.96.122.39 with HTTP; Wed, 5 Nov 2014 11:20:27 -0800 (PST)
Date: Wed, 5 Nov 2014 11:20:27 -0800
Message-ID: <CACox6zCzg+cxJeb+0=2Cskf5e6DkKYkeV4tWsNV-hTdtBRmtpw@mail.gmail.com>
From: lee colleton <lee@colleton.net>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Twitter account lockouts for Tor users
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>

I've noticed that Twitter accounts accessed via Tor have a tendency to lock
due to suspicious activity. This requires a password reset via email or SMS
and may sometimes entail an hour-long delay before Twitter restores access.

I use an alpha[1] Twitter client along with Orbot, both as provided by the
Google Play Store.

Have other Twitter & Tor users seen this same account lock-out?

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

