Delivery-Date: Tue, 19 May 2015 06:31:19 -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 74A6B1E03B5
	for <archiver@seul.org>; Tue, 19 May 2015 06:31:17 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 59B4A354FA;
	Tue, 19 May 2015 10:31:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1729D354F5
 for <tor-talk@lists.torproject.org>; Tue, 19 May 2015 10:31:10 +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 Tx-VB8E1EnQj for <tor-talk@lists.torproject.org>;
 Tue, 19 May 2015 10:31:10 +0000 (UTC)
Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.200])
 (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 CFB73354F1
 for <tor-talk@lists.torproject.org>; Tue, 19 May 2015 10:31:09 +0000 (UTC)
Received: from smtp3.hushmail.com (localhost [127.0.0.1])
 by smtp3.hushmail.com (Postfix) with SMTP id C33EFE023D
 for <tor-talk@lists.torproject.org>; Tue, 19 May 2015 10:31:06 +0000 (UTC)
Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80])
 by smtp3.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Tue, 19 May 2015 10:31:06 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 92E39A2912; Tue, 19 May 2015 10:31:06 +0000 (UTC)
MIME-Version: 1.0
Date: Tue, 19 May 2015 06:31:06 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <447D885D-B966-43F7-B491-19F9E829279B@fb.com>
References: <20150517112641-728-3379-mailpile@mailpile-home>
 <447D885D-B966-43F7-B491-19F9E829279B@fb.com> 
Message-Id: <20150519103106.92E39A2912@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Making a Site Available as both a Hidden Service and
	on the www - thoughts?
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>

>>Oh, there are many, *many* more reasons to have an onion site for
your website than just that. :-)

Such as? A hidden service is by definition hidden. So if you're
willing to have both a HS-front and www-front, how is it that it's not
the only consideration. A tor exit hides the client-origin so besides
the usual e-peen statement that .onion is superior __because__. None
of it matters. As the operator you'll experience complexity, nothing
you wouldn't experience anyway. How did the choice to deploy both HS
and www become about reasons? There are no reasons, none against
anyway. Only consideration of the deployment complexity.

That's like saying a name service for onions is superior to a petname
system. When in truth the statement induces two completely different
objectives. Reasons is not equal to deployment complexity. The title
says "making a site available ass both a HS and WWW". I choose to
ignore the deployment complexity and roll-my-own solution, not ask for
reason for why I might want both.

tl;dr - I agree, it would be great for everyone who has both a www and
HS for a site to use the same methods of solving deployment issues.
Makes it easier to target. Oh, btw, when was the last time facebook
was in the news for privacy violations--yesterday? An onion bought FB
exactly what?

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

