diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-12-07 15:21:38 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-12-07 15:21:38 -0400 |
| commit | 1b20b718fffdbc5c90b7a02e8d389d1fb55c5e47 (patch) | |
| tree | a7e171d1d649635d143315aaca8eaafb5832ce23 | |
| parent | 7a3e845add8c654dbb87fe427afd8655e6681792 (diff) | |
add section on tor speed
| -rw-r--r-- | doc/tips/peer_to_peer_network_with_tor.mdwn | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/doc/tips/peer_to_peer_network_with_tor.mdwn b/doc/tips/peer_to_peer_network_with_tor.mdwn index 718a9218d..3e6a4bd59 100644 --- a/doc/tips/peer_to_peer_network_with_tor.mdwn +++ b/doc/tips/peer_to_peer_network_with_tor.mdwn @@ -63,7 +63,7 @@ so peer1 is a remote of peer2 and peer2 is a remote of peer1. Any number of peers can be connected this way, within reason. -## git-annex remotedaemon +## starting git-annex remotedaemon Notice the `git annex remotedaemon` being run in the above examples. That command runs the Tor hidden service so that other peers @@ -77,6 +77,20 @@ You can do that with a simple cron job: If you use the git-annex assistant, and have it auto-starting on boot, it will take care of starting the remotedaemon for you. +## speed of large transfers + +Tor prioritizes security over speed, and the Tor network only has so much +bandwidth to go around. So, distributing large quantities (gigabytes) +of data over Tor may be slow, and should probably be avoided. + +One way to avoid sending much data over tor is to set up an encrypted +[[special_remote|special_remotes]]. git-annex knows that Tor is rather +expensive to use, so if a file is available on a special remote as well as +over Tor, it will download it from the special remote. + +You can contribute to the Tor network by +[running a Tor relay or bridge](https://www.torproject.org/getinvolved/relays.html.en). + ## onion addresses and authentication You don't need to know about this, but it might be helpful to understand |