]> git.ipfire.org Git - thirdparty/tor.git/commitdiff
speculate about nick's question
authorRoger Dingledine <arma@torproject.org>
Fri, 26 Oct 2007 23:31:05 +0000 (23:31 +0000)
committerRoger Dingledine <arma@torproject.org>
Fri, 26 Oct 2007 23:31:05 +0000 (23:31 +0000)
svn:r12220

doc/TODO

index c06c7dc5ad90ca6d1ddd7c1ac6d6661e8ce1a8cb..176d6ca4ffe4ef25db13618f208bebaa663782e2 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -31,7 +31,11 @@ Things we'd like to do in 0.2.0.x:
       o Change guard calculation
       o Change dir-spec.txt
       - What should we do about hosts that have been up for only 1 hour,
-        but have been up for 100% of that one hour?
+        but have been up for 100% of that one hour? -NM
+        Perhaps the guard flag should only be assigned if the measurement
+        period for that server is at least some large period, like a
+        week; but ignore this exception if "most" servers have too-short
+        measurement periods. -RD
     D 118 if feasible and obvious
     D Maintain a skew estimate and use ftime consistently.
     - 105+TLS, if possible.