X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=49da6ad425cbdea95cb510fc1bca35dea3d72122;hp=3d49ca2ae03e8bb59e1e12139984b7eb5353ff04;hb=b374496daac41b610b0c0d4b2367efbf41880554;hpb=094e75ca11d4e4b02119e38ae88448bcc7fc5b6d diff --git a/TODO b/TODO index 3d49ca2a..49da6ad4 100644 --- a/TODO +++ b/TODO @@ -1,14 +1,12 @@ -$Id: TODO,v 1.145 2016/03/17 10:54:18 fabiankeil Exp $ - Some Privoxy-related tasks, sorted by the time they have been added, not by priority. The latest version should be available at: -http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO +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: -http://www.privoxy.org/faq/general.html#DONATE +https://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. @@ -53,9 +51,6 @@ http://www.privoxy.org/faq/general.html#DONATE 14) Allow to filter POST parameters. -15) If trusted CGI pages are requested without trusted referrer, - set the status code to 403 instead of 200. - 16) Filter SSL encrypted content as well. At the beginning we could use a unencrypted connection between @@ -105,7 +100,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. @@ -129,15 +124,21 @@ 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. + 2016-04: The SF mailing lists have been deprecated, the new ones + are available at: https://lists.privoxy.org/ 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. @@ -156,8 +157,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. @@ -167,6 +168,9 @@ http://www.privoxy.org/faq/general.html#DONATE 68) Use standard make syntax so we don't depend on GNU make. 69) Update autoconf setup (or move away from it). + Unfortunately the autoconf files can't be simply updated + due to license issues: + https://lists.privoxy.org/pipermail/privoxy-devel/2016-April/000008.html 70) If the server connection is reset but the headers are received, consider passing the mess to the client instead @@ -212,7 +216,7 @@ http://www.privoxy.org/faq/general.html#DONATE 82) Detect if the system time goes back in time let the user know if it caused any connections to get closed. -85) Once #84 is done, write a script that populates a directory with +85) Once #51 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. @@ -342,7 +346,7 @@ http://www.privoxy.org/faq/general.html#DONATE running out of stack space, causing the kernel to kill Privoxy ungracefully. -121) Add HTTP/2 support. As a first step, incomming HTTP/1.x requests +121) Add HTTP/2 support. As a first step, incoming HTTP/1.x requests should be translated to outgoing HTTP/2 requests where possible (and if desired by the user). Interested donors: 1. @@ -408,7 +412,7 @@ http://www.privoxy.org/faq/general.html#DONATE 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 + rather neat. https://github.com/NuxiNL/cloudlibc 142) Remove or update the "internal" pcre version. @@ -433,6 +437,41 @@ http://www.privoxy.org/faq/general.html#DONATE currently can result in client requests to config.privoxy.org on the Internet which may not be desirable. +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. + +152) Fix CSS references in the website documentation. + For many pages p_doc.css is specified twice using different paths. + Usually at least one works, but not all of them do and the + duplicated requests are pointless even if they don't end up with + a 404. + +153) Catch SIGINT and use it to close the listen socket, serve + remaining connections and shut down. This would allow higher + uptime and make testing more convenient. + +154) Underline links in docs and cgi pages. More precisely, + don't mess with the browser defaults for link underlining. + +155) The sig_handler() shouldn't call log_error(). + While it isn't known to cause actual problems in normal operation, + it's technically incorrect and causes crashes when running in + valgrind. + +156) Reject socks requests with an explicit error message similar + to the one used for ftp. Motivation: + https://lists.privoxy.org/pipermail/privoxy-users/2017-March/000195.html + +158) Use a single thread to wait for new requests on reused client connections. + Currently the thread that handles the first request on a connection + stays responsible for the client connect until it gets closed. + In case of lots of idle connections lots of waiting threads are used. + While it's conceivable that this ineffiency is irrelevant from a + performance point of view, using a single thread should reduce Privoxy's + memory footprint a bit which may be noticeable in case of multi-user setups + with hundreds of idle connections. ########################################################################## Hosting wish list (relevant for #53)