-$Id: TODO,v 1.125 2014/10/16 11:55:45 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.
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.
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.
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?
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
+
+149) Use poll() for socket selection so the number of sockets Privoxy
+ can deal with isn't limited to FD_SETSIZE anymore.
+
+150) Add blacklistd support.
+
+151) Let the dok-tidy target work cross-platform without introducing
+ a ton of white-space changes that hide the content changes.
+
##########################################################################
Hosting wish list (relevant for #53)
projects / privoxy.git / blobdiff