nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-28 06:13:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

remove some done items; mark some other items as done

Browse Source 
svn:r12438
This commit is contained in:
Roger Dingledine 2007-11-08 16:36:49 +00:00
parent c3a745951b
commit 46273c9080
1 changed files with 5 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/TODO
View File

@ -32,11 +32,6 @@ Here's a go:
median WFU of the set. In addition, anybody born more than a month ago median WFU of the set. In addition, anybody born more than a month ago
who has >=50% WFU is always a winner. 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: For Tor 0.2.0.11-alpha:
- Put a consensus in place of the empty fallback-consensus file in - Put a consensus in place of the empty fallback-consensus file in
src/config and see what breaks. src/config and see what breaks.
@ -97,9 +92,9 @@ Things we'd like to do in 0.2.0.x:
- Protocol revision. - Protocol revision.
- Earliest stages of 110 (infinite-length) in v2 protocol: - Earliest stages of 110 (infinite-length) in v2 protocol:
add support for RELAY_EARLY. add support for RELAY_EARLY.
- Before the feature freeze: (Roger) o Before the feature freeze: (Roger)
- Make tunnelled dir conns use begin_dir if enabled o Make tunnelled dir conns use begin_dir if enabled
- make bridge users fall back from bridge authority to direct attempt o make bridge users fall back from bridge authority to direct attempt
- get more v3 authorities before 0.2.0.x comes out. - get more v3 authorities before 0.2.0.x comes out.
- brainstorm about who those should be - brainstorm about who those should be
@ -107,7 +102,7 @@ Things we'd like to do in 0.2.0.x:
- Bugs. - Bugs.
- Bug reports Roger has heard along that way that don't have enough - Bug reports Roger has heard along that way that don't have enough
details/attention to solve them yet. 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 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. 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 - 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 I believe this is the result of confusion about whether to use
relaybandwidth or bandwidthrate to control bandwidth usage for relaybandwidth or bandwidthrate to control bandwidth usage for
servers. Chances are, this isn't a bug per se. [phobos] 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 unreachable is bunk -- it's leftover from the time when all
servers ran 24/7. now it triggers every time a server goes servers ran 24/7. now it triggers every time a server goes
away and then returns before the old descriptor has expired. away and then returns before the old descriptor has expired.