From sickness@tiscali.it Fri Jul 6 02:32:37 2018 From: sickness To: cypherpunks-legacy@lists.cpunks.org Subject: Re: [tahoe-dev] keeping private grids privatey Date: Fri, 06 Jul 2018 02:32:37 +0000 Message-ID: <172289271885.3881296.18298610602819177024.generated@mail.pglaf.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2355380830045836371==" --===============2355380830045836371== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit > > Setting up a private i2p network might be getting OT. But I'd be > interested as well in finding out how to setup a private i2p network > if you ever figure out or find documentation on how to boot strap one > for your community, please share the documentation on how its done ;) > > Thanks, > Jimmy. > sure, it was discussed multiple times on i2p forums: http://forum.i2p2.de/viewtopic.php?p=13603#13603 http://forum.i2p2.de/viewtopic.php?t=2547 http://forum.i2p2.de/viewtopic.php?t=2381 (the same could be done with tor and freenet, iirc but you don't have tahoe over those, and even if freenet is able to store content, it's fixed to k=1 h=3 s=3 speaking in tahoe-lafs language, and you don't really have a way to repair/check the shares if not by redownloading the entire content over time, it's more like a big cache... but differences between tahoe and freenet were already discussed by zooko in another post) _______________________________________________ tahoe-dev mailing list tahoe-dev(a)tahoe-lafs.org http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev ----- End forwarded message ----- -- Eugen* Leitl leitl http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE --===============2355380830045836371==--