-$Id: TODO,v 1.137 2015/12/27 16:41:17 fabiankeil Exp $
+$Id: TODO,v 1.146 2016/03/30 11:15:02 fabiankeil Exp $
Some Privoxy-related tasks, sorted by the time they
have been added, not by priority.
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.
This should be good enough for most of the content the
user would want to filter.
- Interested donors: 1.
+ Interested donors: 2.
19) enable-forward-fallback. Syntax? Suggested by K.R.
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.
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.
+ Interested donors: 1.
102) Add an include directive to split the config file into several parts.
121) Add HTTP/2 support. As a first step, incomming HTTP/1.x requests
should be translated to outgoing HTTP/2 requests where possible
(and if desired by the user).
+ Interested donors: 1.
122) Allow customized log messages.
an action so the behaviour can be enabled on a per-request basis.
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: 2.
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
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.
+146) Allow to save the internal client tag state to disk and
+ load it after restarts.
- 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).
+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.
- Interested donors: 1.
+148) Add a config directive to change the CGI_SITE_2_HOST
+ (default: config.privoxy.org).
-146) Once #144 is implemented, optionally allow to save the opt-in
- status to disk.
+ 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.
##########################################################################