X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=9760f1cddd27bef39a009c6eb90c4ebdb103fe80;hp=d296c54ccf7e90ef1b6b12b643bf04c4eddc481e;hb=875adf39fba5fad0dc9786a89bc61b0035292555;hpb=0776d25431f66a2e2dfe61d1af22a89ac5e9cff4 diff --git a/TODO b/TODO index d296c54c..9760f1cd 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.117 2014/06/25 10:08:13 fabiankeil Exp $ +$Id: TODO,v 1.142 2016/02/02 13:12:33 fabiankeil Exp $ Some Privoxy-related tasks, sorted by the time they have been added, not by priority. @@ -6,6 +6,10 @@ have been added, not by priority. The latest version should be available at: http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO +There's work in progress to fund development on these items using +donations. If you want to donate, please have a look at: +http://www.privoxy.org/faq/general.html#DONATE + 1) Add more regression tests. Filters should be tested automatically (variables too). Could probably reuse large parts of Privoxy-Filter-Test. Note that there is currently work in progress to leverage curl's @@ -43,6 +47,8 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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. @@ -59,6 +65,8 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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? @@ -112,9 +120,9 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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. @@ -131,8 +139,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO Using Git would also have the advantage that SF now pretends to support it, so we could do it independently from 53). -55) Apply for Coverity scans: http://scan.coverity.com/ - 58) Move more template strings from the code into the actual templates. 59) Import the German template translation. @@ -206,9 +212,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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. @@ -275,6 +278,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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. @@ -341,6 +345,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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. @@ -357,7 +362,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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 @@ -378,9 +383,67 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 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. +133) Consider allowing bitcoin donations. + Interested donors: 2. + +134) Track the total number of bytes written to and received from a socket. + +135) Add OpenBSM audit support. + +136) Make builds reproducible. + +137) Add a (preferably vector-based) logo. + +138) Bring back the scripts to provide actions file feedback. + + Once upon a time (~2003) there were scripts on the webserver + to make reporting action file feedback more convenient for the + user and the actual reports more useful for the developers. + They have been unusable for years and have thus been disabled, + 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)