X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=e2aaadc6e241ef7578c1c5b49fd69843c718aed4;hp=5b791601f5e6b13109b59a29ec31eea9e16c8b6b;hb=08ad8304651556ba3168d4b99b5cd7ef53446ae4;hpb=3e28dfdd76a773f824ea0d39ede00fa808f0f06c diff --git a/TODO b/TODO index 5b791601..e2aaadc6 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.136 2015/12/27 13:32:02 fabiankeil Exp $ +$Id: TODO,v 1.151 2016/06/22 12:21:20 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? @@ -101,7 +105,7 @@ http://www.privoxy.org/faq/general.html#DONATE Figure out a way to solve this. Introduce a cwd config option? 41) Change documentation framework to one that works cross-platform. - Evaluate WML. + Evaluate WML and txt2tags. 42) Add a DTrace USDT provider. Now that FreeBSD has userland DTrace support there's no longer any reason not to. @@ -125,15 +129,19 @@ http://www.privoxy.org/faq/general.html#DONATE It would probably also make sense to look into what other projects did when migrating away from SF. - 2014-05-13: Work in progress. Hosting wish list at the end - of this file. + 2014-05: Work in progress. Hosting wish list at the end + of this file. Looks like most of the other projects + that left SF had lower standards and moved to hosters + that don't come close to sattisfying the requirements. + 2016-03: The website has been moved away from SF infrastructure + and is also available through https:// now. + 2016-04: Server rent for a year has been sponsored by ChameleonJohn. 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. @@ -152,8 +160,8 @@ http://www.privoxy.org/faq/general.html#DONATE is no legal entity. 65) Polish Website. Probably involves ditching the Docbook - mess in favour of wml. There are already several threads - in the mailinglist archives about this. See also #41. + mess. There are already several threads in the mailinglist + archives about this. See also #41. 66) Stop hard-coding the number of action and filter files. @@ -274,6 +282,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. @@ -340,6 +349,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. @@ -377,14 +387,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. - 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: 1. + Interested donors: 2. 134) Track the total number of bytes written to and received from a socket. @@ -403,6 +407,10 @@ 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 @@ -411,23 +419,31 @@ http://www.privoxy.org/faq/general.html#DONATE 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. +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). - 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. + 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. - 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. +149) Use poll() for socket selection so the number of sockets Privoxy + can deal with isn't limited to FD_SETSIZE anymore. -145) Once #144 is implemented, allow clients to opt-in to the - tagging for a limited amount of time (or number of requests). +150) Add blacklistd support. -146) Once #144 is implemented, optionally allow to save the opt-in - status to disk. +151) Let the dok-tidy target work cross-platform without introducing + a ton of white-space changes that hide the content changes. ##########################################################################