Public I2P grid will be usable with Tahoe-LAFS 1.12.0

[Paul Rabahy]

How would this work if a node had an introducer on both i2p and tcp?
Does the node would just connect to all the other nodes that it hears
about from either introducer?

On 9/19/2016 7:18 AM, str4d wrote:
> Hey all!
> 
> tl;dr: if you want to connect to the public I2P grid with 1.12.0 when it
> is released (or trunk until then), ensure that this introducer is in
> your list:
> 
> pb://exupps5kk3amc5iq4q6f5ahggkm4s5fl@i2p:oj7cffq5fnk46iw3i3h2sdgncxrqbxm7wh6i4h2cbpmqsydygkcq.b32.i2p/introducer
> 
> ----
> 
> The next release of Tahoe-LAFS will at long last include native support
> for Tor and I2P clients! Thanks so much to the Tahoe devs who has worked
> to get this over the line :) I've been excited about this because it
> means that the existing public grid on I2P can finally start to keep
> pace with upstream releases.
> 
> The only compatibility issue between 1.12.0 and the existing grid was in
> storage node addressing. The patch used by the I2P grid treated I2P
> addresses as hostnames, so a FURL looked like this:
> 
> pb://TUB_ID@longaddress.b32.i2p/spamandeggs
> 
> In the new architecture of 1.12.0, the FURLs instead look like this:
> 
> pb://TUB_ID@i2p:longaddress.b32.i2p/spamandeggs
> 
> This meant that 1.12.0 FURLs announced to existing I2P storage nodes
> would be considered invalid, and existing FURLs announced to 1.12.0
> nodes would be interpreted as TCP addresses, and be unresolvable.
> 
> Fortunately, I've been running 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 at my introducer FURL (listed above), and by
> using it, your 1.12.0 client will be able to discover the 1.10.0 (and
> 1.9.2!) storage nodes that make up our public grid. So if you include my
> introducer in your list (1.12.0 has multi-introducer support too! Yay!),
> then you will be able to connect to the grid as long as my introducer is
> up. And if you run one of the other I2P introducers, upgrade your
> introducer to my custom build in order to support the newer clients!
> 
> Cheers,
> str4d
> 
> 
> 
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20161226/f53e4072/attachment.sig>