summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-11-08 16:36:49 +0000
committerRoger Dingledine <arma@torproject.org>2007-11-08 16:36:49 +0000
commit46273c908020144d683365b956bfa9950b815296 (patch)
tree539ff1dcd89c05e2932e5905bceca134d44dda3d
parentc3a745951b881c159289a964370c6e7b2f31671c (diff)
downloadtor-46273c908020144d683365b956bfa9950b815296.tar.gz
tor-46273c908020144d683365b956bfa9950b815296.zip
remove some done items; mark some other items as done
svn:r12438
-rw-r--r--doc/TODO15
1 files changed, 5 insertions, 10 deletions
diff --git a/doc/TODO b/doc/TODO
index 958c7b0eb7..6fe91756d3 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -32,11 +32,6 @@ Here's a go:
median WFU of the set. In addition, anybody born more than a month ago
who has >=50% WFU is always a winner.
- o If 1.5*MaxCircuitDirtiness is more than KeepAlive, do we then send
- a KeepAlive and reset our timeout, thus never reaching 1.5*MCD?
- o Aw, crud. We could keep track of how long it's been since
- we last did anything _other_ than a keepalive, I guess. -NM
-
For Tor 0.2.0.11-alpha:
- Put a consensus in place of the empty fallback-consensus file in
src/config and see what breaks.
@@ -97,9 +92,9 @@ Things we'd like to do in 0.2.0.x:
- Protocol revision.
- Earliest stages of 110 (infinite-length) in v2 protocol:
add support for RELAY_EARLY.
- - Before the feature freeze: (Roger)
- - Make tunnelled dir conns use begin_dir if enabled
- - make bridge users fall back from bridge authority to direct attempt
+ o Before the feature freeze: (Roger)
+ o Make tunnelled dir conns use begin_dir if enabled
+ o make bridge users fall back from bridge authority to direct attempt
- get more v3 authorities before 0.2.0.x comes out.
- brainstorm about who those should be
@@ -107,7 +102,7 @@ Things we'd like to do in 0.2.0.x:
- Bugs.
- Bug reports Roger has heard along that way that don't have enough
details/attention to solve them yet.
- - tup said that when he set FetchUselessDescriptors, after
+ o tup said that when he set FetchUselessDescriptors, after
24 or 48 hours he wasn't fetching any descriptors at all
anymore. This was in 0.2.0 but worked fine in 0.1.2.
- arma noticed that when his network went away and he tried
@@ -122,7 +117,7 @@ Things we'd like to do in 0.2.0.x:
I believe this is the result of confusion about whether to use
relaybandwidth or bandwidthrate to control bandwidth usage for
servers. Chances are, this isn't a bug per se. [phobos]
- - this notion of authorities notifying servers that they're
+ o this notion of authorities notifying servers that they're
unreachable is bunk -- it's leftover from the time when all
servers ran 24/7. now it triggers every time a server goes
away and then returns before the old descriptor has expired.