Remove an obsolete newstuff marker

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 455d21c..cb2cdad 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.56 2011/09/18 14:41:03 fabiankeil Exp $
+$Id: TODO,v 1.62 2012/03/18 15:44:57 fabiankeil Exp $

 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.


@@ -211,9 +211,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 
 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.
 
 84) Flesh out the user-manual delivery to serve pages from
     other directories, too.
 


@@ -281,3 +278,26 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 98) When showing action section on the CGI pages, properly escape
     line breaks so they can be copy&pasted into action files without
     adjustments.
 98) When showing action section on the CGI pages, properly escape
     line breaks so they can be copy&pasted into action files without
     adjustments.

+
+99) Figure out a mechanism through which a user can easily enable
+    site-specific action sections that are too aggressive to be
+    enalbled by default. This could be similiar to the presettings
+    in default.action, but could also be just another action file
+    that isn't used by default.
+
+100) Create a cross-platform Privoxy control program and retire
+     the win32 GUI. Integrate support for Privoxy-Regression-Test,
+     Privoxy-Log-Parser, Privoxy-Filter-Test, uagen and similar tools.
+
+101) Forward known client headers in a predefined order that can
+     be changed in the config file. Optionally use a random order.
+     Tools like p0f v3 use the header order for User-Agent detection
+     and thus changing the User-Agent doesn't fool them.
+
+102) Add an include directive to split the config file into several parts.
+
+103) Potential performance improvement for large action files:
+     when figuring out which actions apply, check the action bitmask
+     before pattern matching and skip section that wouldn't modify the
+     actions already set. To increase the impact the sections would have
+     to be applied in reverse.