From d279fb82e20bf89c2edb6485eacd8b6e0fe69971 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Wed, 7 Nov 2007 21:51:21 +0000 Subject: r16550@catbus: nickm | 2007-11-07 16:50:02 -0500 "And $499 for knowing where to hit it." Fix bug 546. svn:r12425 --- doc/TODO | 3 +++ 1 file changed, 3 insertions(+) (limited to 'doc/TODO') diff --git a/doc/TODO b/doc/TODO index 694279afb..547a70a2d 100644 --- a/doc/TODO +++ b/doc/TODO @@ -23,6 +23,9 @@ Items blocking 0.2.0.10-alpha: in 0.2.1.x. - Should we ship with a fallback-consensus? Where in the tarball does it go? What's the process for choosing it? + - We can, but we don't have to now. Stick it in place of the + empty fallback-consensus file in src/config if you like. + - To choose, just grab the most recent consensus you have. - If 1.5*MaxCircuitDirtiness is more than KeepAlive, do we then send a KeepAlive and reset our timeout, thus never reaching 1.5*MCD? - "When reporting clock skew, and we only have a lower bound on -- cgit v1.2.3