X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=TODO;h=1a202675575e08381bcad4f35e012cb9184d2f67;hb=dc80a8219d68d1e25821219e0b3b5bcda5bae21e;hp=262c342461abfef4bc697140441bad5491b4f15d;hpb=38dbf7e5ff2c91c23be30a58e6a17546fdffede4;p=privoxy.git

diff --git a/TODO b/TODO
index 262c3424..1a202675 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.127 2014/10/21 15:31:32 fabiankeil Exp $
+$Id: TODO,v 1.138 2016/01/16 12:29:51 fabiankeil Exp $
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
@@ -47,6 +47,8 @@ http://www.privoxy.org/faq/general.html#DONATE
 11) CGI templates should use semantically-correct HTML
     and scale properly.
 
+    Work in progress.
+
 12) Support pipelining for outgoing connections.
 
 14) Allow to filter POST parameters.
@@ -63,6 +65,8 @@ http://www.privoxy.org/faq/general.html#DONATE
     This should be good enough for most of the content the
     user would want to filter.
 
+    Interested donors: 1.
+
 19) enable-forward-fallback. Syntax? Suggested by K.R.
 
 21) User Manual delivery doesn't accept multiple slashes. Should it?
@@ -116,9 +120,9 @@ http://www.privoxy.org/faq/general.html#DONATE
     macros with strstr() before compiling pcrs commands.
     Investigated, needs some restructuring but is probably worth it.
 
-51) Make user-manual directive more generic to allow serving
-    the FAQ and other stuff, too. Consider changing the port
-    for "same origin policy" issues.
+51) Make user-manual directive more generic to allow serving the FAQ
+    and files from user-specified directories. Consider changing the
+    port for "same origin policy" issues.
 
 53) Find a more reliable hoster. Involves finding out what our
     requirements are and which SF alternatives fulfil them.
@@ -208,9 +212,6 @@ http://www.privoxy.org/faq/general.html#DONATE
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 
-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.
@@ -359,7 +360,7 @@ http://www.privoxy.org/faq/general.html#DONATE
 126) Run the Co-Advisor HTTP compliance tests, evaluate the results,
      fix the compliance issues that aren't by design and document
      the rest.
-     Note that Privoxy developers qualified for free account upgrades:
+     Note that Privoxy developers qualify for free account upgrades:
      http://coad.measurement-factory.com/details.html#pricing
 
 127) Add "real" CGI support (serve program output instead of forwarding
@@ -381,10 +382,13 @@ http://www.privoxy.org/faq/general.html#DONATE
      Interested donors: 1.
 
 132) Provide a Tor hidden service to reach the Privoxy website.
+     Work in progress: http://jvauzb4sb3bwlsnc.onion/
+     This hidden service serves a copy of the www.privoxy.org content
+     (filtered through Privoxy to replace some absolute URLs).
      Interested donors: 1.
 
 133) Consider allowing bitcoin donations.
-     Interested donors: 1.
+     Interested donors: 2.
 
 134) Track the total number of bytes written to and received from a socket.
 
@@ -403,6 +407,36 @@ http://www.privoxy.org/faq/general.html#DONATE
      but making the reporting mechanism available again would be a
      good idea.
 
+141) Port Privoxy to CloudABI, which, despite the name, is actually
+     rather neet. https://github.com/NuxiNL/cloudlibc
+
+142) Remove or update the "internal" pcre version.
+
+143) Add support for OpenBSD's pledge feature once it's stablelized.
+     This should be a lot less work then #124.
+
+144) Allow Privoxy admins to pre-define tags that are be set for
+     clients that previously opted-in through the CGI interface.
+
+     This would be useful in multi-user setups where admins may
+     want to allow users to disable certain actions and filters
+     for themselves without affecting others.
+
+     Even in single-user setups this could be useful to allow
+     more fine-grained toggling. For example to disable request
+     blocking while still crunching cookies, or to disable
+     experimental filters only.
+
+     Interested donors: 1.
+
+145) Once #144 is implemented, allow clients to opt-in to the
+     tagging for a limited amount of time (or number of requests).
+
+     Interested donors: 1.
+
+146) Once #144 is implemented, optionally allow to save the opt-in
+     status to disk.
+
 ##########################################################################
 
 Hosting wish list (relevant for #53)