X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=5b791601f5e6b13109b59a29ec31eea9e16c8b6b;hp=c6a5e90bb158e9e433cadb346224841591d401c2;hb=3e28dfdd76a773f824ea0d39ede00fa808f0f06c;hpb=8e7e6abc094a59de61ae06793517b3142a9d1b6c diff --git a/TODO b/TODO index c6a5e90b..5b791601 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.125 2014/10/16 11:55:45 fabiankeil Exp $ +$Id: TODO,v 1.136 2015/12/27 13:32:02 fabiankeil Exp $ Some Privoxy-related tasks, sorted by the time they have been added, not by priority. @@ -8,11 +8,7 @@ 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.spi-inc.org/donations/ - -If you have any questions regarding donations please either mail to -the public user mailing list (ijbswa-users@lists.sourceforge.net) or -to Privoxy's SPI liason Fabian (fk@fabiankeil.de). +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. @@ -120,9 +116,9 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de). 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. @@ -212,9 +208,6 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de). 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. @@ -363,7 +356,7 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de). 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 @@ -385,6 +378,9 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de). 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. @@ -398,6 +394,41 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de). 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. + +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. + +145) Once #144 is implemented, allow clients to opt-in to the + tagging for a limited amount of time (or number of requests). + +146) Once #144 is implemented, optionally allow to save the opt-in + status to disk. + ########################################################################## Hosting wish list (relevant for #53)