Delivery-Date: Thu, 03 Jul 2014 01:12:22 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 C67961E0AB7
	for <archiver@seul.org>; Thu,  3 Jul 2014 01:12:19 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3F6B72F62E;
	Thu,  3 Jul 2014 05:12:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6746728B2B
 for <tor-talk@lists.torproject.org>; Thu,  3 Jul 2014 05:04:05 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 91kanVQdYMUW for <tor-talk@lists.torproject.org>;
 Thu,  3 Jul 2014 05:04:05 +0000 (UTC)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com
 [IPv6:2607:f8b0:400c:c03::22e])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 44D0028ADE
 for <tor-talk@lists.torproject.org>; Thu,  3 Jul 2014 05:04:05 +0000 (UTC)
Received: by mail-vc0-f174.google.com with SMTP id hy4so11110607vcb.19
 for <tor-talk@lists.torproject.org>; Wed, 02 Jul 2014 22:04:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=AuhzlaWjN/prq+KNhbSu//N2GRSn9IEh/GGFaX9s8R8=;
 b=uZbSohVw4LZYoH9FPncFJ5l0Q7rch4RFZg+k62obvb6vxWhy89qJRu9kU5LI/YomJ0
 wTF8oXB9cdRgcMMQIHg1HJdKVB7VLbxWZNDA8tko6i1y2zOR4daFZXA7wmrQFZKv8Z9N
 6iAfRd59FCDk43I3mO7hAaEWgna+O2G40/VPXaQetqZFdqNketwu++NtvrjRBaSmyAc8
 dPLooc+5tUY3L4b4MflwMcTQYtI+peFXLdGg9g6ONQ0Q68Dr4HoStvK4xePmrug3r4bb
 rCS7xhZIZVg2HJrhf8adFDJV9miFkVzfX3PbXtTXmKNf5L/1DgwGKv3pf0hXA1Y+g5+1
 mdOg==
MIME-Version: 1.0
X-Received: by 10.52.252.193 with SMTP id zu1mr1374710vdc.7.1404363842742;
 Wed, 02 Jul 2014 22:04:02 -0700 (PDT)
Received: by 10.221.65.198 with HTTP; Wed, 2 Jul 2014 22:04:02 -0700 (PDT)
In-Reply-To: <CAP3fC8TUmMGFOnyXNRWzR30ynk_bxFod0_VwcKAtguDESi70Fg@mail.gmail.com>
References: <53AB742E.5000400@riseup.net>
 <DUB121-W1602424B2673FF14097129C8180@phx.gbl>
 <53ABAAFA.1040406@riseup.net>
 <C21E9389-F7C9-47E7-B475-A3D23C8C4F14@hidemeta.com>
 <20140626073045.GA10980@inner.h.apk.li>
 <6334967458078911169@unknownmsgid>
 <CAP3fC8TUmMGFOnyXNRWzR30ynk_bxFod0_VwcKAtguDESi70Fg@mail.gmail.com>
Date: Thu, 3 Jul 2014 01:04:02 -0400
Message-ID: <CAD2Ti2_L++oBpNgb4ga8qYE6yKqx4KSGoGJTP5nKUfhJKU-_dA@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] High-latency hidden services (was: Re: Secure Hidden
 Service (was: Re: ... Illegal Activity As A Metric ...))
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 Wed, Jul 2, 2014 at 7:18 PM, Helder Ribeiro <helder@discor.de> wrote:
> On Sun, Jun 29, 2014 at 9:58 PM, Seth David Schoen <schoen@eff.org> wrote:
>> Then a question is whether users would want to use a service that takes,
>> say, several hours to act on or answer their queries (and whether the
>> amount of padding data required to thwart end-to-end traffic analysis
>> is acceptable).

I probably missed some context in thread. Link padding doesn't imply
or have a tie to high[er] latency (other than minimal processing overhead).
It's just the usual committed bandwidth, but always full, with wheat,
or backed by chaff when there's not enough wheat to fill it.

> High-latency web browsing is actually a great use case and could
> benefit from the extra security.
>
> Apps like Pocket (http://getpocket.com/) work as a "read it later"
> queue, downloading things for offline reading.

I think it was Freenet where 'web' (page/browsing) was modeled
as a non-real-time-interactive, retrievable (and updateable) object.
Essentially documents. But were delivered in real time over the net.

Torrents seem similar... queing, updatable, latency tolerant. Though
there's no 'hours' delay storage buffer nodes between actual source
and sink either.

Besides mail mixes, what systems use such formal buffers in between?
-- 
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

