Delivery-Date: Thu, 04 Sep 2014 19:43:14 -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_SIGNED,
	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 D7AFA1E0BCD;
	Thu,  4 Sep 2014 19:43:12 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8AE55263F0;
	Thu,  4 Sep 2014 23:43:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 59C1F263D5
 for <tor-talk@lists.torproject.org>; Thu,  4 Sep 2014 23:43:01 +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 xLwojv0Kr1Pd for <tor-talk@lists.torproject.org>;
 Thu,  4 Sep 2014 23:43:01 +0000 (UTC)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com
 [IPv6:2607:f8b0:4001:c03::230])
 (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 39BE52554E
 for <tor-talk@lists.torproject.org>; Thu,  4 Sep 2014 23:43:00 +0000 (UTC)
Received: by mail-ie0-f176.google.com with SMTP id x19so12765891ier.21
 for <tor-talk@lists.torproject.org>; Thu, 04 Sep 2014 16:42:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virgil.gr; s=dkim;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :content-type; bh=PGZJTyMwYMR/vy3OVV4Z910Go23wqRCLFMp6h+xtgog=;
 b=N+sJvjeNoTnt+sBdJvR0rsJNyqkuM0L9r0CAenpQmxYv36EQ3o2gTxbktqgZsJwO6O
 GoF5CvpdhJsN4a+Ar9f++tQ60HWJo/LbdRsi2SE92Ww2BZsSHDIRwoow84dFcCuj5Wig
 +K0Cuu3jd0MPe9+Y7WhdvnEdg4D4OQX1oPU6E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:from:date
 :message-id:subject:to:content-type;
 bh=PGZJTyMwYMR/vy3OVV4Z910Go23wqRCLFMp6h+xtgog=;
 b=MDqbsdeN7g8z5pjiRA+qIa7DAfvJ2jz8cULQRTcNnaggtLqe156U9bKfiWVvyiDaTx
 5uun6nbYTKiYnMLW/hNXN96HOyE8UkLoQSKMwg0QIt5gUce+jX2MoqQ8uzRrxva9Qddf
 w4g+wKfm8m6xesggeVsFVfYbXrNlfUqczwGk0P6qtZYMFsTUtrA2Y2Co9b7JfU/yY+lr
 gzCm0V6btGFIv7IpB22mSH36d5+pqKHmCu2GjGmAKT1vWT5px7EFg8zT0u5ctB0s7nXz
 SL8phm9lG1y4TvSPnEkXL0iw6mUUDp9VRSBcj+W2Dnx6Ryf4hpsOrTbSVkrLZEGGTuFR
 Ywww==
X-Gm-Message-State: ALoCoQk+p8QLHM6I/0mkin3h4iYYfJYWowDWhNk9wWihrpUW3ZeCzuPtcU9t6NYgj0TnMzErj+ev
X-Received: by 10.50.43.164 with SMTP id x4mr11949691igl.27.1409874178600;
 Thu, 04 Sep 2014 16:42:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.50.22.99 with HTTP; Thu, 4 Sep 2014 16:42:37 -0700 (PDT)
In-Reply-To: <5404B09C.8010305@torservers.net>
References: <20140901134422.GA28782@lo.psyced.org>
 <5404B09C.8010305@torservers.net>
From: Virgil Griffith <i@virgil.gr>
Date: Thu, 4 Sep 2014 16:42:37 -0700
Message-ID: <CADop2NFxX=3F_Yw7eLxa1-sQfPs5Le-U7dCV3hM_siVOPiSFgg@mail.gmail.com>
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Micropayment embedded in circuit building? New idea?
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>

Two points.

> I don't think there's a lot of money to be made in the first place

The major proposals I've seen don't aspire to make operating a relay
profitable, but merely *subsidize* the money + time involved in operating a
relay.  I see it akin to automated, decentralized grants akin to the kind
that torservers.net provides.

Would this reduce your opposition (assuming the technical details are
worked out) ?

> at the same time volunteers might step away ("I'm not in it for the
money, but now people can do it for money, so why keep my relay running."),
both also reasons why I'm not really enthusiastic about the whole thing.

A complementary proposal is to such that each circuit has a most one
incentivized relay, or additionally to forbid an incentivized relay from
being the guard node.  It also seems like a darn-good-idea that people who
run unincentivized nodes get special social recognition.

I used to think of incentivizing Tor relays as a big new idea.  But
increasingly I just see it as an automated way of doing what is already
done.  In the simplest case, say if instead of manually mailing operators a
t-shirt, we had an automated process which gave operators a token that
could be redeemed for a t-shirt, that would be fully sufficient for the
incentivization proposals.

That's all I got.
-V
-- 
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

