X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=c894d814d943691665f570b8af2a9db881fdf55f;hp=54227296100bbdc07f351b7f6916650af4f1b16b;hb=191175ab4c347a4edb0432c8fb8bdc9afdf91430;hpb=8038a4eb40ab924eb22ae860ca071eb3942b33fc diff --git a/TODO b/TODO index 54227296..c894d814 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.114 2014/06/16 10:15:32 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. @@ -6,10 +6,15 @@ have been added, not by priority. The latest version should be available at: http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO -1) Add some regression tests. Filters should be tested automatically +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 - test suite which could be used for this as well. + test suite, patches have been submitted upstream: + http://curl.haxx.se/mail/lib-2014-06/0070.html 3) Fix some more XXX: comments. @@ -42,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. @@ -58,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? @@ -111,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. @@ -123,12 +132,11 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 2014-05-13: Work in progress. Hosting wish list at the end of this file. -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). + Interested donors: 1. -55) Apply for Coverity scans: http://scan.coverity.com/ +54) Move away from CVS to a more modern revision control system. + 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. @@ -203,9 +211,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. @@ -272,6 +277,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. @@ -338,6 +344,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. @@ -346,13 +353,15 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 124) Add support for the "lightweight OS capability and sandbox framework" Capsicum. http://www.cl.cam.ac.uk/research/security/capsicum/ + Interested donors: 1. 125) Allow clients to HTTPS-encrypt the proxy connection. + Interested donors: 1. 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 @@ -371,6 +380,57 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 131) The handle-as-empty-doc-returns-ok directive should be replaced with an action so the behaviour can be enabled on a per-request basis. + Interested donors: 1. + +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. + +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 + 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. + +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. ##########################################################################