Delivery-Date: Fri, 13 Feb 2015 18:31:08 -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.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,URIBL_BLOCKED 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 38EBD1E0880
	for <archiver@seul.org>; Fri, 13 Feb 2015 18:31:07 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E891532C24;
	Fri, 13 Feb 2015 23:31:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5AE92325B7
 for <tor-talk@lists.torproject.org>; Fri, 13 Feb 2015 23:30:58 +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 cHMdW2-DE1uB for <tor-talk@lists.torproject.org>;
 Fri, 13 Feb 2015 23:30:58 +0000 (UTC)
Received: from smtp5.hushmail.com (smtp5.hushmail.com [65.39.178.142])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "Self-signed" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 258BE31425
 for <tor-talk@lists.torproject.org>; Fri, 13 Feb 2015 23:30:58 +0000 (UTC)
Received: from smtp5.hushmail.com (localhost [127.0.0.1])
 by smtp5.hushmail.com (Postfix) with SMTP id 1730960224
 for <tor-talk@lists.torproject.org>; Fri, 13 Feb 2015 23:30:55 +0000 (UTC)
Received: from smtp.hushmail.com (w3.hushmail.com [65.39.178.62])
 by smtp5.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Fri, 13 Feb 2015 23:30:54 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id AEB08C040C; Fri, 13 Feb 2015 23:30:54 +0000 (UTC)
MIME-Version: 1.0
Date: Fri, 13 Feb 2015 18:30:54 -0500
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <CADop2NEFxHz1U=5_r4Zffj9Z0oa+EW1QOG61cQoMJMR8NgqCjA@mail.gmail.com>
References: <CADop2NFwg+mViiRWWZWYQo4S8m+d87U10LrvAsQZmuGHTBOGjQ@mail.gmail.com>
 <87r3ttpz37.fsf@riseup.net>
 <CADop2NEFxHz1U=5_r4Zffj9Z0oa+EW1QOG61cQoMJMR8NgqCjA@mail.gmail.com> 
Message-Id: <20150213233054.AEB08C040C@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Funded search engine for onionspace?
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>


>Alas no.  I'm aware this is suboptimal.  I see GOOG search engine as
a
>temporary-ladder just to get the ball rolling.  I am open to using
any
>other index.  For what it's worth I'm very pleased with GOOG's
>performance---right now it's searching an index of 650k onion pages
and the
>number grows every day.

If you instead use a google search appliance couldn't you use google
engine for indexing without having to use google itself? Wouldn't that
also avoid the problem of google queries being associated with the
client making the request?

>Although we technically could read provided passwords, we don't keep
logs
>of passed traffic.  However, I understand that many users don't
understand
>the tor2web threat model.  But this is the same as all Tor2web nodes,
yes?
>This is not at all unique to OnionCity.  As far as I know all Tor2web
nodes
>allow form submissions.

What is unique to onion.city is that access to someonion.onion.city
occurs using http and doesn't redirect to the .onion if Tor is in use.
That the tor2web mirror might snoop is implicit--that the exit (if
using tor) might also snoop is more of a concern.

>You mentioned it'd be better to have it randomly pick among the
available
>Tor2web nodes instead of everything going through OnionCity.  This
breaks
>the GOOG search engine which only wants to return "canonical" URLs. 
We
>could talk about making OnionCity a DNS round-robin akin to how
Tor2web.org
>currently works, but then I'm just replicating Tor2web.

The ability of tor2web to provide mirrors should be optional. If you
only know one mirror and that mirror cannot service the request then
how are you going to get any of the other mirrors? Google engine can
return related addresses in an order based on the success of loading
the mirror itself. If onion.city always works it will tend to precede
tor2web.org. If onion.city goes down (having search front-end separate
from tor2web mirror) the search engine can reorder the result to
improve the success of the first click.

  >Right now I aggregate existing lists of onion sites and put them
into the
>site map.
  >* https://ahmia.fi/onions/
  >* http://skunksworkedp2cg.onion.city/sites.txt
  >* http://xlmvhk3rpdux26dz.onion.city/
  >* http://kkkkkku5juzqh33a.onion.city/

If google is itself handling the indexing won't that cause a problem
for sites in those lists, which are normally okay with being indexed,
just not by googlebot? I for one couldn't care less about being
indexed by ahmia.fi but it'll be a cold day in hell before I let
googlebot. Precisely because of how easy it is to link the search to
the requester.
--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

