+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 clients
+ 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
+ hasn'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, expected to be
+ committed after the 3.0.34 release. Funded with donations
+ made to the Privoxy project.
+
+185) The mbedTLS and OpenSSL versions of generate_host_certificate()
+ should only be called when necessary and the check should be
+ done without holding the certificate mutex.
+
+186) Privoxy should handle "OPTIONS *" requests properly.
+
+187) There should be a convenient way to see the versions of
+ the libraries Privoxy is using.
+
+188) In the windows config.txt file, add the line
+ user-manual ./doc/user-manual/
+ right after
+ # Copyright ...
+ #
+
+189) Bring back binary packages for macOS, preferably for both Intel and M1.
+ The first step would be getting at least one build system, either
+ donated or bought with donations earmarked for this.
+ Interested donors: 0.
+
+190) The socks5 authentication code should send user name an password
+ seperately or we should increase the cbuf size to allow longer
+ user names and passwords.
+
+191) The cipher-list directive should be split into cipher-list-server
+ and cipher-list-client.
+
+192) The client TLS contexts should probably be shared among threads
+ to spend less time and memory loading the root certificates.
+
+193) Use SHA256 instead of MD5 for the host hash used when generating file
+ names for host certificates and keys.
+
+194) There should be a way to force gif deanimation if the server does not
+ declare the content as gif.
+
+195) We should probably cache the server TLS contexts.
+
+196) Investigate if it's worth adding an optional mutex for the CGI handler.
+ Could reduce memory use and increase performance on single core systems
+ for some tests.
+
+197) Investigate if parts of Privoxy should get optional replacements
+ written in Rust.
+
+198) Add a config directive that prevent's IP addresses from being logged
+ (when logging is enabled).
+
+199) In actions.c the "#define DEFINE_ACTION_ALIAS 0" lines should probably
+ be changed to "#undef DEFINE_ACTION_ALIAS" or removed.
+
+200) Add a config directive that causes Privoxy to remove all
+ host certificates before exiting.
+
+201) Add an action to change the trusted-cas-file for a section.
+ This should be useful in countries where a person-in-the-middle
+ attack is known to happen on some domains but should not be tolerated
+ on others. It would also allow to limit the accepted CA certificates
+ for given domains instead of accepting all that are specified with
+ the trusted-cas-file directive.
+
+202) Allow to use multiple log files with different debug settings.
+ Suggested by Jonathan Marten in FR#607.
+