Delivery-Date: Thu, 05 Jun 2014 14:58:31 -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 moria.seul.org (Postfix) with ESMTPS id C27A01E0A54
	for <archiver@seul.org>; Thu,  5 Jun 2014 14:58:29 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DC5672F8B0;
	Thu,  5 Jun 2014 18:58:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F13762F855
 for <tor-talk@lists.torproject.org>; Thu,  5 Jun 2014 18:55:07 +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 YgKW9LDnbwz0 for <tor-talk@lists.torproject.org>;
 Thu,  5 Jun 2014 18:55:07 +0000 (UTC)
Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com
 [IPv6:2607:f8b0:400d:c04::22a])
 (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 CC1832F6C6
 for <tor-talk@lists.torproject.org>; Thu,  5 Jun 2014 18:55:07 +0000 (UTC)
Received: by mail-qg0-f42.google.com with SMTP id q107so2348586qgd.1
 for <tor-talk@lists.torproject.org>; Thu, 05 Jun 2014 11:55:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=1RmI3dYWATWAL+b3+mwEsZUF7CDahiSTMMw9458E2qI=;
 b=s5IQyShSpECPF6xFAG2w/ohQbD9h+llfnphjDhxRF9de78fR4SMLBQROqEpqpwE0h7
 XZhtevDeDbBDq8/smOPVAtFPMfWczgVuNSM240Bo1uXiy8MxnZwQKQxmhKU0vLWv7T8A
 I3G5x4WF9WscVF1EPnL1BFE3xk6f/WCkRscTRSCUZ2PPJorbzBt4rNLeO4Xj2cCVRdT3
 Z7ubcDouwC7oAkC2o4uoW5wpLHz/Gi7DPJ2CrqZloBQWk/XCsZc7KJW2luSv0c6bjsA5
 7wt+m8XNG90QrZLqWdMp7LKDIKaHs21Z9x+ksA5S9kwM+oD3qpEdym1PuGv9KVBsT1zE
 vkfg==
MIME-Version: 1.0
X-Received: by 10.224.38.204 with SMTP id c12mr87279012qae.1.1401994505476;
 Thu, 05 Jun 2014 11:55:05 -0700 (PDT)
Received: by 10.224.72.209 with HTTP; Thu, 5 Jun 2014 11:55:05 -0700 (PDT)
Date: Thu, 5 Jun 2014 12:55:05 -0600
Message-ID: <CAOu3Fjru3rhaM4O+PtVCD0fidaOVAM6nrrJ+bQR8t1BmrqVY5A@mail.gmail.com>
From: Brian Barker <brianbarker3@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Decentralized internet with Tor
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>

Hi Tor Talk,

I've been pondering over some stuff regarding net neutrality, Tor, etc.
 There are a number of people interested in decentralizing the internet via
self-hosted mesh network nodes.  Basically, everyone hosts a node and they
all link up to create a wide-area mesh net.  To summarize my thoughts, I'll
quote what I just posted to /r/darknetplan about this (full post
<http://www.reddit.com/r/darknetplan/comments/27e9h7/mesh_net_with_tor_tor_coin/>
):

I recently wondered why we didn't just make a mass, decentralized network
> by linking self-hosted nodes. As is typical with the internet, a little
> googling and I find others have similar thoughts. I thought I'd share a few
> of my own on this.



CJDNS seems alright, but why not build on some things out there that
> already solve similar problems? We have Tor, which is great at bouncing
> around nodes to get to a distant endpoint, has end-to-end encryption, and
> more. Granted, Tor is currently built to purposefully take a less-efficient
> route in the name of obscurity, but adapting that to a mesh network seems
> less work than starting from scratch.



Getting people to host nodes could be an issue over time. It will take
> hardware, electricity and a sizable crowd of those willing to contribute.
> The Tor group just released their plan for TorCoin
> <https://docs.google.com/file/d/0B7r4osQgWVqKTHdxTlowUVpsVmJRcjF3Y3dtcTVscFhEaW5F/view?sle=true>
>  to deal with this issue. It's a method of mining TorCoins as you host a
> node, using the proof-of-work schemes to verify you contributed a given
> amount to the network. Seems like a great way to make this more popular.


> Lastly, the Grugq has a project called Portal
> <https://github.com/grugq/portal> which configures routers as tor-only
> network nodes. There's also a Raspberry Pi version
> <https://github.com/grugq/PORTALofPi>. These could be a fantastic
> starting point to creating easily-configurable devices to put on the mesh
> net.


I would love to hear more from Tor experts or anyone else interested in how
this could work.
-- 
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

