[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs

[Tahoe-LAFS]

#3888: Handling Tor and i2p in NURLs
--------------------------+-----------------------------------
     Reporter:  itamarst  |      Owner:
         Type:  defect    |     Status:  new
     Priority:  normal    |  Milestone:  HTTP Storage Protocol
    Component:  unknown   |    Version:  n/a
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------------------

Comment (by meejah):

 Yeah, "pb+tor" might be better because it also covers the case where you
 want to use Tor to a clearnet listener. And it's more explicit.

 That said, though, "use tor for client-operations" is more of a client
 decision and doesn't necessarily need to be burned into the NURLS like
 that -- the only time you _need_ to use Tor as a client is when the
 listener is on a .onion

 There's a _lot_ of other stuff to consider regarding "internet location
 privacy" so having e.g. a Tahoe option like "--location-privacy" would be
 more how I'd handle the "tor to clearnet services" situation, because
 there are other things you'd probably want to put over Tor and e.g. make
 sure you're not doing local DNS lookups or similar.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3888#comment:5>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage