Delivery-Date: Sat, 14 Nov 2015 07:55:55 -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 0DC911E03F9;
	Sat, 14 Nov 2015 07:55:53 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B519C387C0;
	Sat, 14 Nov 2015 12:55:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 72D6F38783
 for <tor-talk@lists.torproject.org>; Sat, 14 Nov 2015 12:55:38 +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 27GC3OXXKOdz for <tor-talk@lists.torproject.org>;
 Sat, 14 Nov 2015 12:55:38 +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 53323386DA
 for <tor-talk@lists.torproject.org>; Sat, 14 Nov 2015 12:55:38 +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 35ED21A1E58
 for <tor-talk@lists.torproject.org>; Sat, 14 Nov 2015 04:55:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1447505735; bh=RjLc28xo0lvNeO3lcFKYEF31q7ZipWN7Rxgt391Vw+g=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=lL3thLd1zOiF7iIAEQ4ezYzRkozhvGPPgZxIJDUOtEnpuR7oGe400YqZBF06MDVEH
 VpakmjxPLCTvaMZwCPljsZi9oCYw0STsAi29P35Ghdmz33MG4smg6Ff6ZCU6ctYCpP
 RenQsRX63LPEi9E0vod3hWM2Y3Jd23ckEOT0226w=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id 3252A1C13E0
To: tor-talk@lists.torproject.org
References: <20151112133507.GA16219@inner.h.apk.li>
 <564710D6.6040606@riseup.net> <20151114120019.GG16219@inner.h.apk.li>
From: Mirimir <mirimir@riseup.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <56472F3C.8080902@riseup.net>
Date: Sat, 14 Nov 2015 05:55:24 -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: <20151114120019.GG16219@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/14/2015 05:00 AM, Andreas Krey wrote:
> On Sat, 14 Nov 2015 03:45:42 +0000, Mirimir wrote:
> ...
>> If you must use Twitter via Tor,
> 
> No, I just don't want to use twitter directly
> from workboxes etc.
> 
> Here it seems a bit of an interaction between
> tweetdeck and twitter itself. Tweetdeck
> lets me in but not post, and when I log
> into the original twitter UI it tells
> me to change password. I don't know
> whether there is a time where posting
> doesn't work but I'm not told to change
> PW either and just cannot post.
> 
> Stupid but bearable, all in all.

I've had the same experience. It's probably just a Tweetdeck bug.

>> you can setup a VPS with a minimal LXDE
>> desktop and VNC onion service.
> 
> I've already done something similar. There
> is a hosting (shell account, actually) provider
> here in germany who accepts payments via mail,
> which means I can do ssh -D via tor to there,
> and use their IP towards twitter. Account
> was stable.
> 
> Andreas

Yes, there's a lot less latency with that approach. I was thinking about
using a private VPN via Tor, perhaps as an onion service. But then I got
into the idea of decoupling local-VPS traffic from VPS-Twitter traffic.
To make traffic confirmation harder.
-- 
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

