X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=90b542b4c2e60b85df6b96c3795a1c4e1b9ad78f;hp=8b71433b12f25b5ba0f429635e5b2ecf2824cea4;hb=6e4befd8a7f565c8fa89ab200358e9d802ba687e;hpb=2550d3867dad0af094f9cb17f2466ea53c62dc1e

diff --git a/TODO b/TODO
index 8b71433b..90b542b4 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.143 2016/02/13 11:18:15 fabiankeil Exp $
+$Id: TODO,v 1.147 2016/04/06 12:39:14 fabiankeil Exp $
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
@@ -129,15 +129,19 @@ http://www.privoxy.org/faq/general.html#DONATE
     It would probably also make sense to look into what other
     projects did when migrating away from SF.
 
-    2014-05-13: Work in progress. Hosting wish list at the end
-    of this file.
+    2014-05: Work in progress. Hosting wish list at the end
+             of this file. Looks like most of the other projects
+             that left SF had lower standards and moved to hosters
+             that don't come close to sattisfying the requirements.
+    2016-03: The website has been moved away from SF infrastructure
+             and is also available through https:// now.
+    2016-04: Server rent for a year has been sponsored by ChameleonJohn.
 
     Interested donors: 1.
 
 54) Move away from CVS to a more modern revision control system.
-    Find out if there are any objection against going with Git.
-    Using Git would also have the advantage that SF now pretends
-    to support it, so we could do it independently from 53).
+    The move to git is work in progress:
+    https://sourceforge.net/p/ijbswa/mailman/message/34994343/
 
 58) Move more template strings from the code into the actual templates.
 
@@ -415,27 +419,8 @@ http://www.privoxy.org/faq/general.html#DONATE
 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.
+146) Allow to save the internal client tag state to disk and
+     load it after restarts.
 
 147) Improve "Building from Source" section in the user manual.
      A common problem seems to be that it's not obvious to non-technical
@@ -444,7 +429,13 @@ http://www.privoxy.org/faq/general.html#DONATE
      technical users (like Privoxy developers) who want to install or test
      Privoxy on platforms they are not familiar with.
 
-146) Once #145 is implemented, allow clients to specify the time.
+148) Add a config directive to change the CGI_SITE_2_HOST
+     (default: config.privoxy.org).
+
+     If Privoxy is used as reverse proxy or intercepting proxy without
+     getting intercepted requests, error pages created from default templates
+     currently can result in client requests to config.privoxy.org on the
+     Internet which may not be desirable.
 
 ##########################################################################