aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSteven Murdoch <Steven.Murdoch@cl.cam.ac.uk>2010-03-15 17:50:50 +0000
committerRoger Dingledine <arma@torproject.org>2010-09-30 22:04:52 -0400
commitac552473501c8c56f0b6a653528ca0879bb20bdd (patch)
tree99e7467261e234dd204e5133ad3f31b3f5f94c12 /doc
parentd3d411533cb0aa630e888a398ec096017fe94c52 (diff)
downloadtor-ac552473501c8c56f0b6a653528ca0879bb20bdd.tar.gz
tor-ac552473501c8c56f0b6a653528ca0879bb20bdd.zip
Integrate more feedback from IRC
- For now we are only talking about moving clients to be bridges - Some questions on how we should inform users
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt b/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
index 05d65ce156..8563b47547 100644
--- a/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
+++ b/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
@@ -14,6 +14,11 @@ Target:
preferences. The proposal also defines the new controller messages
and options which will control this process.
+ Note that for the moment, only transitions between client and
+ bridge are being considered. Transitions to public relay will
+ be considered at a future date, but will use the same
+ infrastructure for measuring capacity and reliability.
+
2. Motivation and history
Tor has a growing user-base and one of the major impediments to the
@@ -108,3 +113,11 @@ Target:
- Perhaps the bridge authority should tell potential bridges
whether to enable themselves, by taking into account whether
their IP address is blocked
+
+ - How do we explain the possible risks of running a bridge/relay
+ * Use of bandwidth/congestion
+ * Publication of IP address
+ * Blocking from IRC (even for non-exit relays)
+
+ - What feedback should we give to bridge relays, to encourage then
+ e.g. number of recent users (what about reserve bridges)?