X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=8b71433b12f25b5ba0f429635e5b2ecf2824cea4;hp=262c342461abfef4bc697140441bad5491b4f15d;hb=529f359abd088b2a8e2c5e3631f688f2220f4e20;hpb=38dbf7e5ff2c91c23be30a58e6a17546fdffede4 diff --git a/TODO b/TODO index 262c3424..8b71433b 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.143 2016/02/13 11:18:15 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: 2. + 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. @@ -277,6 +278,7 @@ http://www.privoxy.org/faq/general.html#DONATE 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. @@ -343,6 +345,7 @@ http://www.privoxy.org/faq/general.html#DONATE 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. @@ -359,7 +362,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 @@ -380,11 +383,8 @@ http://www.privoxy.org/faq/general.html#DONATE 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. - 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 +403,49 @@ 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. + +146) Once #145 is implemented, allow clients to specify the time. + ########################################################################## Hosting wish list (relevant for #53)