GSoC 2015 to overcome NAT limitations?

[David Stainton]

Hi Lukas,

I'm very interested to see what the tahoe-devs say to this idea of
participating in GSoC.

With regards to NAT... it seems that they decided a while back that
this problem was outside the scope of what Tahoe-LAFS should solve...
but maybe they are interested? I can tell you that there are various
people such as myself who use Tahoe-LAFS with Tor and Tor hidden
services... we therefore get NAT penetration for free. I don't know
much about I2p but I think they may have NAT penetration as well.

Cheers,

David


On Wed, Feb 25, 2015 at 4:20 PM, Lukas Pirl <tahoe-dev at lukas-pirl.de> wrote:
> Hello Tahoe-People!
>
> What if I'd be interested in contributing to Tahoe-LAFS in the context
> of this year's Google Summer of Code¹?
>
> What is interesting for me is the firewall/NAT/hole punching topic. From
> what I recognize, running Tahoe behind some NAT is relatively popular
> (e.g. at home). From my own experiences, I can say that the peer-to-peer
> idea is somewhat destroyed if one runs most of the nodes behind a NAT.
>
> Well, there are five days left for you as an organization to apply for
> this year's Summer of Code. Tahoe can definitely profit!
>
> Further, I have a (early) question about the mentoring. Do you want the
> mentor to be a Tahoe core developer (what definitely would make perfect
> sense) or am I supposed/can I ask one of my folks in preference? And if
> so, is it sufficient for mentors to be wizards in Python and to have
> joined the GSoC already or should they have made contributions to Tahoe
> already?
>
> I'd be happy to hear from you!
>
> Kind regards,
>
> Lukas
>
> ¹ https://www.google-melange.com/gsoc/homepage/google/gsoc2015
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev