I don't like this idea for 1 main reason -> My IP address changes. I know that some people use/see Tahoe-lafs as a client/server protocol, but I see it as a p2p protocol. If I need to re-setup my node every time I take my laptop to a coffee shop, that would be very inconvenient. The thing that feels the most like a server to me is the introducer, but since I have been controlling the public test grid I know that the ip address has changed at least 4 times and I lost control of the DNS name at least once.
Final thought, in a p2p environment, auto detecting IP addresses locally doesn't work very well anyway because of NAT. As long as their is an introducer, I believe that the most accurate way to get your own IP address is to ask the introducer what it is. (Don't get me wrong, I like the idea of supporting TOR and making TOR configuration easier.) On Mon, Aug 31, 2015 at 8:30 AM, Lukas Pirl <[email protected]> wrote: > On 09/01/2015 12:22 AM, Daira Hopwood wrote: > >> I am concerned about this being a significant usability regression. >> > > I thought so too > (but didn't feel I am into that enough to note that). > > _______________________________________________ > tahoe-dev mailing list > [email protected] > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev >
_______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
