Delivery-Date: Sat, 14 Nov 2015 05:46:04 -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.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 E198B1E03F9;
	Sat, 14 Nov 2015 05:46:02 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D6AFB3854D;
	Sat, 14 Nov 2015 10:45:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D09C138532
 for <tor-talk@lists.torproject.org>; Sat, 14 Nov 2015 10:45:55 +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 vThNEV0hPtLL for <tor-talk@lists.torproject.org>;
 Sat, 14 Nov 2015 10:45:55 +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 B0B2437ADF
 for <tor-talk@lists.torproject.org>; Sat, 14 Nov 2015 10:45:55 +0000 (UTC)
Received: from piha.riseup.net (unknown [10.0.1.163])
 (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 1AFAB1A1A03
 for <tor-talk@lists.torproject.org>; Sat, 14 Nov 2015 02:45:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1447497953; bh=c4h9EoXHfTAODSZqmOIBf6VsDzAVfxB0LNtlXLXBpn8=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=Y94dxYiEJeCJU3OQD/NnxU+Kbcj5E23N4blv3vaB/RByfSBMI+mKUqkurGXbisU0P
 9EtOd14TF9z2PIAUgftWY9rByL11L/fV68bX7AJiVop8GAf8kFJUtO8MrMXZ0miBnJ
 B9zPZsD5yuq0ESHvSAKpyHLqHrW6oU2TYrAHaJHE=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id 9F7921C07DB
To: tor-talk@lists.torproject.org
References: <20151112133507.GA16219@inner.h.apk.li>
From: Mirimir <mirimir@riseup.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <564710D6.6040606@riseup.net>
Date: Sat, 14 Nov 2015 03:45:42 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151112133507.GA16219@inner.h.apk.li>
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
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 11/12/2015 06:35 AM, Andreas Krey wrote:
> Hi all,
> 
> datapoints: The last week twitter (via tweetdeck.twitter.com)
> looked normal. I could log in and see my feed, but I couldn't
> post anything any more ('suspicious activity'). Once I got
> blocked and needed to use a mailed password token.
> 
> An acquaintance retried an account he had used some time
> ago, and it is now logged and requires to immediately
> add a phone number to send an unlock key.
> 
> His account was only ever used via tor, mine is used
> only via tor for years, and from my iphone.
> 
> This all feels very stupid.
> 
> Andreas

If you must use Twitter via Tor, you can setup a VPS with a minimal LXDE
desktop and VNC onion service.

http://dbshmc5frbchaum2.onion/Remote-LXDE-Desktop.html
-- 
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

