ing one of the grid's multiple introducers
for years, so nearly all existing grid nodes use it. I have created a
fork of 1.11.0 that rewrites old-style FURLs in announcements to
new-style, and vice versa:
https://github.com/str4d/tahoe-lafs/tree/i2p-grid-migration
I am running this build a
but I think they may have NAT
> penetration as well.
Yes, we do have NAT penetration if UDP is enabled.
str4d
>
> Cheers,
>
> David
>
>
> On Wed, Feb 25, 2015 at 4:20 PM, Lukas Pirl
> wrote:
>> Hello Tahoe-People!
>>
>> What if I'd be int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Natanael wrote:
> Den 17 feb 2015 07:56 skrev "str4d" :
>
>> Other than that, there is no difference. Non-honest Tahoe-LAFS
>> nodes are perfectly capable of joining a standard Tahoe-LAFS
>> network and sending
uld cause the DNS lookups of hostnames for
regular Tahoe-LAFS nodes to fail, or (at a lower level) prevent
connections to known Tahoe-LAFS node IPs. So I still don't see how I2P
Tahoe-LAFS is any weaker that standard Tahoe-LAFS.
str4d
>
>
>
> ___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey Zooko and David,
I was busy over the past several weeks, but my timetable has settled
down. And yep, DST has altered my availability. I am generally
available from 21:00 UTC most days, but can meet at 20:00 UTC if that
is better.
str4d
tickets on the Tahoe-LAFS bug tracker about both
the multi-introducer system, and a no-introducers system. One (or
both) of these should eventually get merged into Tahoe-LAFS.
str4d
On 03/11/2014 02:28 PM, Zancas Dearana wrote:
> On Sun, Mar 9, 2014 at 7:59 PM, xiao_s_yuan
> wrote:
>
tahoe create-introducer ~/.tahoe/introducer
$ tahoe start -d ~/.tahoe-client
$ tahoe start --node-directory=/home/user/.tahoe/introducer
(Some commands support appending the node directory. All commands IIRC
support "-d", "--node-directory=" )
str4d
On 11/12/2013 09:24 PM, Ed
