Delivery-Date: Sat, 25 Apr 2015 13:48:35 -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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,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 C1B121E08B9
	for <archiver@seul.org>; Sat, 25 Apr 2015 13:48:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E9E1C34EC5;
	Sat, 25 Apr 2015 17:48:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4BECA34BA2
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 17:48:26 +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 1RCTsZZpCM5A for <tor-talk@lists.torproject.org>;
 Sat, 25 Apr 2015 17:48:26 +0000 (UTC)
Received: from smtp2.hushmail.com (smtp2.hushmail.com [65.39.178.134])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "smtp.hushmail.com" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 1DCBE34B9E
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 17:48:25 +0000 (UTC)
Received: from smtp2.hushmail.com (localhost [127.0.0.1])
 by smtp2.hushmail.com (Postfix) with SMTP id D1F19A01B9
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 17:48:22 +0000 (UTC)
Received: from smtp.hushmail.com (w7.hushmail.com [65.39.178.32])
 by smtp2.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 17:48:22 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id BA18A40C08; Sat, 25 Apr 2015 17:48:22 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 25 Apr 2015 13:48:22 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <5539FE14.8040503@sophiehassfurther.com>
References: <20150416215238.37FBBC03DD@smtp.hushmail.com>
 <55315DC9.50802@sophiehassfurther.com>
 <20150424000609.73C53E04DA@smtp.hushmail.com>
 <5539FE14.8040503@sophiehassfurther.com> 
Message-Id: <20150425174822.BA18A40C08@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] TorBirdy seems to connect to the same exit node
	again and again
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>

Hi Sophie,

>Options b) and c) would be very luxurious, but option a) really 
>solved my problem, and seems quite important for those who 
>come from a different background.

There's a strong correlation between the perceived usefulness to
end-users and their support for a FOSS project :) A simple warning is
easy enough.

>Other things that come to mind:
>"Test proxy settings" could be somewhere more prominent, 
>for users like me :) I am the kind of person that does not
>disable the warning message that pops up when clicking on 
>the TorBirdy preferences.
>
>I am -manually- logging what exit ports TorBirdy uses, out of 
>curiosity.
>I will keep you posted in case something weird happens again.

I was wondering if that was going to come up. The ip check hidden
behind a warning dialog hinders obtaining useful data. I'll keep that
in mind. Logging information on success and failure to use an exit
would be a useful for debugging (and finding problematic exits).
Thanks for the input.

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

