diff options
| author | Roger Dingledine <arma@torproject.org> | 2007-10-26 23:31:05 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2007-10-26 23:31:05 +0000 |
| commit | 5f54a9f7f664e8218d84d3f486e56e5f1f5737ff (patch) | |
| tree | 43ce45f05756a89e0c1e0bec6777d36c1c693723 | |
| parent | 8fa70711217d60c7c157f0c1311cda2391498168 (diff) | |
| download | tor-5f54a9f7f664e8218d84d3f486e56e5f1f5737ff.tar tor-5f54a9f7f664e8218d84d3f486e56e5f1f5737ff.tar.gz | |
speculate about nick's question
svn:r12220
| -rw-r--r-- | doc/TODO | 6 |
1 files changed, 5 insertions, 1 deletions
@@ -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. |