X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=TODO;h=68fcfd6150edc2d99035571a2c207eeeab1af450;hb=433e0b9bc1c17e50196d6d55fbb2bc293f8777c7;hp=9bf091d3519228acfdf46ea102055debf72e94d3;hpb=849b5faec9b956ce234440d177f5eef89c13ef36;p=privoxy.git

diff --git a/TODO b/TODO
index 9bf091d3..68fcfd61 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.21 2010/11/06 11:55:49 fabiankeil Exp $
+$Id: TODO,v 1.28 2010/12/14 18:56:11 fabiankeil Exp $
 
 Some Privoxy related task, not ordered in any way.
 
@@ -103,7 +103,8 @@ Some Privoxy related task, not ordered in any way.
 41) Change documentation framework to one that works cross-platform.
     Evaluate WML.
 
-42) Add DTrace hooks.
+42) Add DTrace hooks. Now that FreeBSD has userland DTrace
+    support there's no longer any reason not to.
 
 43) Write a tool to check URL patterns against URLs in the log file.
     This could be included in Privoxy-Regression-Test.
@@ -138,7 +139,8 @@ Some Privoxy related task, not ordered in any way.
     http://coad.measurement-factory.com/details.html#pricing
 
 57) Allow piping into external programs to allow more powerful
-    filters and policy decisions.
+    filters and policy decisions. Incomplete support available
+    in Fabian's popen branch.
 
 58) Move more template strings from the code into the actual templates.
 
@@ -196,3 +198,41 @@ Some Privoxy related task, not ordered in any way.
 
 80) Change FEATURE_EXTENDED_HOST_PATTERNS to support both
     extended and vanilla host patterns at the same time.
+
+    Note that the requirement is to allow the user to decide
+    if the domain pattern should be interpreted as regex or
+    traditional host pattern and if it's not obvious that the
+    user made any decision, default to the latter.
+
+    Possible solutions would be:
+
+    1. An always-use-regex-domain-patterns config option
+    2. An enable-regex-domain-patterns-for-this-action-file option
+    3. An enable-regex-domain-patterns-for-this-action-file-until-the-user-says-otherwise option
+    4. A treat-the-domain-pattern-in-this-line-as-regex(-or-not) option
+    5. Combinations of the options above
+
+    With 2+4, 3+4 or 2+3+4 being the preferences until
+    further discussion.
+
+81) Merge Fabian's unlimited-config-lines branch.
+
+82) Detect if the system time goes back in time let the user
+    know if it caused any connections to get closed.
+
+83) Make the FAQ available through the CGI interface like the
+    user manual is.
+
+84) Flesh out the user-manual delivery to serve pages from
+    other directories, too.
+
+85) Once #84 is done, write a script that populates a directory with
+    various common third-party icons (stumbleupon.png, facebook.png ...)
+    and redirect requests for them to Privoxy.
+
+86) Add a server-body-tagger action. This is trivial as as all the
+    functionallity required to do it already exists.
+
+87) Add a client-body-tagger action. This is less trivial as we currently
+    don't buffer client bodies. After 14) is implemented it would be
+    trivial, though.