X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=4455c2ac66311d2063c11ac65c762dbea8b8890e;hp=9243287029bfaf461578c4e8e45707eac3c1af4c;hb=41bcde325feaf65a42fe2c4ab21cee5771ac60ad;hpb=694302ba33c361b948db3ab1f17d77dc7eb6e9b6 diff --git a/TODO b/TODO index 92432870..4455c2ac 100644 --- a/TODO +++ b/TODO @@ -6,13 +6,14 @@ https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob_plain;f=TODO;hb=HEAD There's work in progress to fund development on these items using donations. If you want to donate, please have a look at: -https://www.privoxy.org/faq/general.html#DONATE +https://www.privoxy.org/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, patches have been submitted upstream: - http://curl.haxx.se/mail/lib-2014-06/0070.html + https://curl.se/mail/lib-2014-06/0070.html + https://curl.se/mail/lib-2021-01/0068.html 3) Fix some more XXX: comments. @@ -49,8 +50,6 @@ https://www.privoxy.org/faq/general.html#DONATE 12) Support pipelining for outgoing connections. -14) Allow to filter POST parameters. - 19) enable-forward-fallback. Syntax? Suggested by K.R. 21) User Manual delivery doesn't accept multiple slashes. Should it? @@ -188,9 +187,7 @@ https://www.privoxy.org/faq/general.html#DONATE 86) Add a server-body-tagger action. This is trivial as as all the functionality required to do it already exists. -87) Add a client-body-tagger action. This is less trivial as we currently - don't buffer client bodies. After 14) is implemented it would be - trivial, though. +87) Add a client-body-tagger action. This, too, is trivial. 88) Investigate if there's a Perl module that Privoxy-Regression-Test could optionally use to keep connections alive, preferably while @@ -344,8 +341,6 @@ https://www.privoxy.org/faq/general.html#DONATE 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 @@ -359,9 +354,6 @@ https://www.privoxy.org/faq/general.html#DONATE 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 neat. 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. @@ -440,6 +432,54 @@ https://www.privoxy.org/faq/general.html#DONATE like pcre and MbedTLS. Required for #142. Somewhat related: https://lists.privoxy.org/pipermail/privoxy-devel/2020-November/000400.html +167) Set up a public Privoxy-Filter-Test instance. + +168) Add a privacy policy. + +169) Preserve all relevant copyright and license statements in binary + packages we distribute. + +170) Serve the ca-cert-file through the CGI interface so client's + can conveniently import it (insecurely). + +171) Create a "view page using Privoxy" website where users can input + an URL and get a screenshot of a browser fetching the URL + through Privoxy. + +172) Create a public git repository for Privoxy-Filter-Test. + +173) Document Privoxy's governance model. + +174) Let the Tor Onion Service for the privoxy website + serve gitweb and the git repository as well. + +175) Add more screenshots to the documentation and website. + +176) Find a new fiduciary sponsor as a replacement for Zwiebelfreunde e.V., + so that we can continue to receive tax-deductible donations in Europe. + +177) Support https-inspection for intercepted requests. + +178) Warn on http://config.privoxy.org/client-tags if a Tag name + has't at least one matching action section. + +179) Add a add-server-header{} action to add headers to the response + sent to the client (including responses generated by Privoxy itself). + +180) Add support for GnuTLS. + +181) Allow to upgrade an http request to https behind the + client's back using a client-header filter. + +182) Before enforcing the client-header-order, check that the + client headers actually need sorting. Should reduce log + messages and memory allocations. + +183) Properly deal with proxy responses that arrive in multiple pieces + when https inspecting while using a forwarding proxy. + +184) Add support for wolfSSL. Work in progress. + ########################################################################## Hosting wish list (relevant for #53)