Delivery-Date: Fri, 24 Apr 2015 18:56:43 -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,
	LOTS_OF_MONEY,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 3685D1E0BDF
	for <archiver@seul.org>; Fri, 24 Apr 2015 18:56:42 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D62BA34C70;
	Fri, 24 Apr 2015 22:56:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id EA7B734876
 for <tor-talk@lists.torproject.org>; Fri, 24 Apr 2015 22:56:34 +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 nMbVPh1q1Uez for <tor-talk@lists.torproject.org>;
 Fri, 24 Apr 2015 22:56:34 +0000 (UTC)
Received: from vfemail.net (ninezero.vfemail.net [96.30.253.190])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id D5129347D9
 for <tor-talk@lists.torproject.org>; Fri, 24 Apr 2015 22:56:34 +0000 (UTC)
Received: (qmail 94514 invoked by uid 89); 24 Apr 2015 22:56:32 -0000
Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1)
 by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP;
 24 Apr 2015 22:56:32 -0000
Received: (qmail 94436 invoked by uid 89); 24 Apr 2015 22:56:15 -0000
Received: by simscan 1.3.1 ppid: 94434, pid: 94435, t: 0.0021s scanners:none
Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62)
 by FreeQueue with SMTP; 24 Apr 2015 22:56:15 -0000
Received: (qmail 31207 invoked by uid 89); 24 Apr 2015 22:56:15 -0000
Received: by simscan 1.4.0 ppid: 31201, pid: 31204, t: 0.0239s scanners:none
Received: from unknown (HELO localhost)
 (Z29vZnl6cm5zc21AdmZlbWFpbC5uZXQ=@172.16.100.93)
 by 172.16.100.62 with ESMTPA; 24 Apr 2015 22:56:15 -0000
Received: from 176.10.99.201 ([176.10.99.201]) by www.vfemail.net (Horde
 Framework) with HTTP; Fri, 24 Apr 2015 17:56:15 -0500
Message-ID: <20150424175615.37693mrjmwzqyivk@www.vfemail.net>
Date: Fri, 24 Apr 2015 17:56:15 -0500
From: goofyzrnssm@vfemail.net
To: tor-talk@lists.torproject.org
References: <d06f575323abeaf1c540f473dfb93b30@smtp.hushmail.com>
 <553aa590.02138d0a.0a5a.0345@mx.google.com>
In-Reply-To: <553aa590.02138d0a.0a5a.0345@mx.google.com>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.2)
X-VFEmail-Originating-IP: 176.10.99.201
X-VFEmail-AntiSpam: Notify admin@vfemail.net of any spam, and include
 VFEmail headers
Subject: Re: [tor-talk] Clarification of Tor's involvement with DARPA's	Memex
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="Yes"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Roger Dingledine:
> And to be clear, I think this is a great trend: we need to make onion
> services easier to understand and more accessible (and faster and more
> robust) for ordinary people, or we'll remain stuck with all the metaphors
> that include the word 'dark'.

Realizing that there are many different considerations of which I'm  
not aware, (also that this is a feature request of sorts, so please do  
point me in the right direction here) I for one would really like to  
see TBB automatically translate (for example) "3g2upl4pq6kufc4m.onion"  
into the human readable "DuckDuckGo," perhaps in a similar manner as  
with EV SSL cert's, though perhaps only for location-known and  
the-content-is-legal-everywhere onion services.

Perhaps some sort of opt-in procedure would be reasonable for those  
high-security-yet-not-location-anonymous onion services who really  
would rather be more easily identified?  That would save the users'  
time of verifying their .onion URL's at least (plus, it could possibly  
decrease any phishing / link-jacking opportunities as well).

It just seems like all the information is already there, in the Tor  
world, that if .onion site operators are okay with being found  
geographically... then why keep their business names hidden from the  
browser?  Vote cast.

cheers,
gz


-------------------------------------------------

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  
-- 
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

