[tahoe-lafs-trac-stream] [Tahoe-LAFS] #517: make tahoe Tor- and I2P-friendly

[Tahoe-LAFS]

#517: make tahoe Tor- and I2P-friendly
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  ioerror
         Type:           |     Status:  new
  enhancement            |  Milestone:  undecided
     Priority:  minor    |    Version:  1.2.0
    Component:  code-    |   Keywords:  privacy anonymity anti-censorship
  network                |  i2p tor-protocol usability
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 Or, for history, one syntax which got a -0 (for being kinda YAGNI) was to
 declare that any `[connections]` key that matched `(\w+)\.socks-proxy`
 would cause a Foolscap plugin to get installed that routes `$1`-type
 connection hints to the given SOCKS proxy (and a similar thing for CONNECT
 proxies). Then Tahoe wouldn't know anything special about Tor or I2P, it'd
 just be the names of the tahoe.cfg keys that mattered. That would let
 users add new connection types in the future without changing the Tahoe
 code. We felt that people aren't adding new anonymous-router systems very
 often (for good reasons), and there are other Tor/I2P-specific things that
 probably *will* require special handling (like launching a Tor daemon when
 Tahoe starts up), so the benefit wouldn't really be worth it.

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