Delivery-Date: Mon, 15 Feb 2016 11:04:12 -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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 B9E011E0B07;
	Mon, 15 Feb 2016 11:04:10 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4BBF6391A7;
	Mon, 15 Feb 2016 16:04:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 67A14391A5
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 16:04:02 +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 tMbbVTIlYS2j for <tor-talk@lists.torproject.org>;
 Mon, 15 Feb 2016 16:04:02 +0000 (UTC)
Received: from paulo.mayfirst.org (paulo.mayfirst.org [209.234.253.240])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 519B721428
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 16:04:02 +0000 (UTC)
Received: from paulo.mayfirst.org (unknown [127.0.0.1])
 by paulo.mayfirst.org (Postfix) with ESMTP id AAF2F3F2D
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 11:03:59 -0500 (EST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender:
 nathanfreitas@paulo.mayfirst.org) with ESMTPSA id 9F1183F2C
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
 by mailauth.nyi.internal (Postfix) with ESMTP id AD806201F5
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 11:03:58 -0500 (EST)
Received: from web5 ([10.202.2.215])
 by compute3.internal (MEProxy); Mon, 15 Feb 2016 11:03:58 -0500
Received: by web5.nyi.internal (Postfix, from userid 99)
 id 90619A7312D; Mon, 15 Feb 2016 11:03:58 -0500 (EST)
Message-Id: <1455552238.2101715.521740874.4039A5C2@webmail.messagingengine.com>
X-Sasl-Enc: nRVZYzwDmBmbEghYRQIacWgwY03SPTCOInIISLJ02ccu 1455552238
From: Nathan Freitas <nathan@freitas.net>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
X-Mailer: MessagingEngine.com Webmail Interface - ajax-aeec9b65
In-Reply-To: <512753.dcda490e4edbc4f6d4e8d62b65c0a6eba9c97bd0@popretr.messagingengine.com>
References: <512753.dcda490e4edbc4f6d4e8d62b65c0a6eba9c97bd0@popretr.messagingengine.com>
 <56C19C8C.4050608@cryptolab.net>
Date: Mon, 15 Feb 2016 11:03:58 -0500
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [tor-talk] Default to meek based on location?
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 Mon, Feb 15, 2016, at 04:38 AM, rizzo wrote:
> In some big censored countries, meek pluggable transports are the only
> option to connect to the Tor network without manually obtaining
> bridges, a process which I believe many people don't understand enough
> to figure it out on their own. Has there been any discussion on
> whether meek could be made the default or at least recommended option
> when configuring Tor for the first time from certain locations? Could
> we detect the local time zone and then recommend a way to connect
> based on location?

I think the recent Tor Browser releases have done a better job of
walking people through the process of enabling bridges on setup. Adding
some additional logic based on time zone, language setting, etc, would
be a useful idea to gently nudge people towards using bridges by
default. In addition, I think better error handling of failed Tor
connection would be useful ("It looks like you are having a problem
connecting to Tor, and that Tor may be blocked. Can we try an alternate
approach?").

I am working through these ideas right now with Orbot, because the
amount of support emails I receive that basically say "Tor is stuck at
10%" is a bit overwhelming. Often telling them to enable bridges of some
sort, solves the issue.

+n
-- 
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

