bump copyright date

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 1ad3d6d..f3100bc 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.132 2015/08/12 10:38:16 fabiankeil Exp $
+$Id: TODO,v 1.140 2016/01/21 14:06:20 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?
@@ -384,7 +388,7 @@ http://www.privoxy.org/faq/general.html#DONATE
      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,11 +407,47 @@ http://www.privoxy.org/faq/general.html#DONATE
      but making the reporting mechanism available again would be a
      good idea.
 
+140) Toggling Privoxy off currently also disables stuff that
+     probably shouldn't be affected (such as actions like
+     forward-override). Investigate and fix or document.
+
 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.
+
+147) Improve "Building from Source" section in the user manual.
+     A common problem seems to be that it's not obvious to non-technical
+     users how the listed dependencies can be installed on the commonly
+     used platforms. Adding a couple of examples should also be useful for
+     technical users (like Privoxy developers) who want to install or test
+     Privoxy on platforms they are not familiar with.
+
 ##########################################################################
 
 Hosting wish list (relevant for #53)