From: hal9 Date: Wed, 5 Jun 2002 00:33:07 +0000 (+0000) Subject: Just catching up. Nothing significantly new. X-Git-Tag: v_3_1_archive_branchpoint~240 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=332bea234759493659457e0293ebb12d5cfa13be Just catching up. Nothing significantly new. --- diff --git a/AUTHORS b/AUTHORS index f6700066..229582dc 100644 --- a/AUTHORS +++ b/AUTHORS @@ -13,16 +13,18 @@ Current Project Developers: Current Project Contributors: Rodrigo Barbosa (RPM specfiles) + Moritz Barsnick Hal Burgiss (docs) Alexander Lazic Gábor Lipták Guy Haroon Rafique + Roland Rosenfeld David Schmidt (OS/2, Mac OSX ports) Joerg Strohmayer Sarantis Paskalis -Originally developed by: +Based in part on code originally developed by: Junkbusters Corp. Anonymous Coders @@ -31,16 +33,20 @@ Thanks to the many people who have tested Privoxy, reported bugs, or made suggestions. These include (in alphabetical order): Ken Arromdee + Devin Bayer Reiner Buehl Andrew J. Caines Clifford Caoile + Michael T. Davis Peter E Aaron Hamid Magnus Holmgren Paul Lieverse Roberto Ragusa + Maynard Riley Bart Schelstraete Darren Wiebe + jwz If we've missed you off this list, please let us know! diff --git a/README b/README index 705c989c..40c2190e 100644 --- a/README +++ b/README @@ -31,27 +31,13 @@ * *********************************************************************/ -This README is included with the development version of Privoxy 2.9.15, which -will eventually become Privoxy v3.0 (and soon we hope!). See http:// -www.privoxy.org/ for more information. The current code level is beta, and -seems stable to us :). +This README is included with the development version of Privoxy 3.1.1, which +will eventually become Privoxy v3.2. See http://www.privoxy.org/ for more +information. The current code level is alpha, and may break in mysterious ways +:) There may be features only partially implemented, or worse, not functional. ------------------------------------------------------------------------------- -Table of Contents -1. IMPORTANT CHANGES -2. INSTALL -3. RUN -4. CONFIGURATION -5. DOCUMENTATION -6. CONTACTING THE DEVELOPERS, BUG REPORTING AND FEATURE REQUESTS - - 6.1. Get Support - 6.2. Report bugs - 6.3. Request new features - 6.4. Report ads or other filter problems - 6.5. Other - Privoxy is a web proxy with advanced filtering capabilities for protecting privacy, filtering web page content, managing cookies, controlling access, and removing ads, banners, pop-ups and other obnoxious Internet junk. Privoxy has a @@ -85,8 +71,8 @@ compiler like gcc are required. When building from a source tarball (either release version or nightly CVS tarball), first unpack the source: - tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz] - cd privoxy-2.9.15-beta + tar xzvf privoxy-3.1.1-beta-src* [.tgz or .tar.gz] + cd privoxy-3.1.1-beta For retrieving the current CVS sources, you'll need CVS installed. Note that sources from CVS are development quality, and may not be stable, or well @@ -129,28 +115,31 @@ For binary RPM installation, and other platforms, see the user-manual as well. privoxy [--help] [--version] [--no-daemon] [--pidfile PIDFILE] [--user USER [.GROUP]] [config_file] -See the man page or user-manual for a brief explanation of each option. +See the man page or User Manual for an explanation of each option, and other +configuration and usage issues. If no config_file is specified on the command line, Privoxy will look for a file named 'config' in the current directory (except Win32 which will look for 'config.txt'). If no config_file is found, Privoxy will fail to start. -Or for Red Hat: /etc/rc.d/init.d/privoxy start +Or for Red Hat based distributions: /etc/rc.d/init.d/privoxy start Or for SuSE: /etc/rc.d/privoxy start +Or Debian: /etc/init.d/privoxy start + ------------------------------------------------------------------------------- 4. CONFIGURATION See: 'config', 'default.action', 'user.action', and 'default.filter'. -'user.action' is for personal configuration. These are all well commented. Most -of the magic is in '*.action' files. 'user.action' should be used for any -actions customizations. On Unix-like systems, these files are installed in /etc -/privoxy. On Windows, then wherever the executable itself is installed. There -are many significant changes and advances since Junkbuster v2.0.x. The -user-manual has a run down of configuration options, and examples: http:// -www.privoxy.org/user-manual/. +'user.action' is for personal and local configuration preferences. These are +all well commented. Most of the magic is in '*.action' files. 'user.action' +should be used for any actions customizations. On Unix-like systems, these +files are installed in /etc/privoxy. On Windows, then wherever the executable +itself is installed. There are many significant changes and advances since +Junkbuster v2.0.x. The User Manual has an explanation of all configuration +options, and examples: http://www.privoxy.org/user-manual/. Be sure to set your browser(s) for HTTP/HTTPS Proxy at :, or whatever you specify in the config file under 'listen-address'. DEFAULT is localhost: @@ -166,13 +155,13 @@ development process. 5. DOCUMENTATION -There should be documentation in the 'doc' subdirectory, but it is not -completed at this point. In particular, see the user-manual there, the faq, and +There should be documentation in the 'doc' subdirectory, but it may not be in +sync with current code. In particular, see the User Manual there, the FAQ, and those interested in Privoxy development, should look at developer-manual. The most up to date source of information on the current development version, -may still be either comments in the source code, or the included configuration -files. The source and configuration files are all well commented. The main +may be either comments in the source code, or the included configuration files. +The source and configuration files are all well commented. The main configuration files are: 'config', 'default.action', and 'default.filter' in the toplevel source directory. @@ -182,63 +171,70 @@ Included documentation may vary according to platform and packager. 6. CONTACTING THE DEVELOPERS, BUG REPORTING AND FEATURE REQUESTS -We value your feedback. However, to provide you with the best support, please -note the following sections. +We value your feedback. In fact, we rely on it to improve Privoxy and its +configuration. However, please note the following hints, so we can provide you +with the best support: ------------------------------------------------------------------------------- 6.1. Get Support -To get support, use the Sourceforge Support Forum: +For casual users, our support forum at SourceForge is probably best suited: +http://sourceforge.net/tracker/?group_id=11118&atid=211118 - http://sourceforge.net/tracker/?group_id=11118&atid=211118 +All users are of course welcome to discuss their issues on the users mailing +list, where the developers also hang around. ------------------------------------------------------------------------------- -6.2. Report bugs +6.2. Report Bugs -To submit bugs, use the Sourceforge Bug Forum: +Please report all bugs only through our bug tracker: http://sourceforge.net/ +tracker/?group_id=11118&atid=111118. - http://sourceforge.net/tracker/?group_id=11118&atid=111118. +Before doing so, please make sure that the bug has not already been submitted +and observe the additional hints at the top of the submit form. -Make sure that the bug has not already been submitted. Please try to verify -that it is a Privoxy bug, and not a browser or site bug first. If you are using -your own custom configuration, please try the stock configs to see if the -problem is a configuration related bug. And if not using the latest development -snapshot, please try the latest one. Or even better, CVS sources. Please be -sure to include the Privoxy version, platform, browser, any pertinent log data, -any other relevant details (please be specific) and, if possible, some way to -reproduce the bug. +Please try to verify that it is a Privoxy bug, and not a browser or site bug +first. If unsure, try toggling off Privoxy, and see if the problem persists. +The appendix of the user manual also has helpful information on action +debugging. If you are using your own custom configuration, please try the stock +configs to see if the problem is configuration related. -------------------------------------------------------------------------------- +If not using the latest version, chances are that the bug has been found and +fixed in the meantime. We would appreciate if you could take the time to +upgrade to the latest version (or even the latest CVS snapshot) and verify your +bug, but this is not required for reporting. -6.3. Request new features +------------------------------------------------------------------------------- -To submit ideas on new features, use the Sourceforge feature request forum: +6.3. Request New Features - http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse. +You are welcome to submit ideas on new features or other proposals for +improvement through our feature request tracker at http://sourceforge.net/ +tracker/?atid=361118&group_id=11118. ------------------------------------------------------------------------------- -6.4. Report ads or other filter problems +6.4. Report Ads or Other Actions-Related Problems -You can also send feedback on websites that Privoxy has problems with. Please -bookmark the following link: "Privoxy - Submit Filter Feedback". Once you surf -to a page with problems, use the bookmark to send us feedback. We will look -into the issue as soon as possible. +Please send feedback on ads that slipped through, innocent images that were +blocked, and any other problems relating to the default.action file through our +actions feedback mechanism located at http://www.privoxy.org/actions/. On this +page, you will also find a bookmark which will take you back there from any +troubled site and even pre-fill the form! New, improved default.action files will occasionally be made available based on -your feedback. These will be announced on the ijbswa-announce list. +your feedback. These will be announced on the ijbswa-announce list and +available from our project page. ------------------------------------------------------------------------------- 6.5. Other -For any other issues, feel free to use the mailing lists: - - http://sourceforge.net/mail/?group_id=11118. - -Anyone interested in actively participating in development and related -discussions can also join the appropriate mailing list. Archives are available, -too. See the page on Sourceforge. +For any other issues, feel free to use the mailing lists. Technically +interested users and people who wish to contribute to the project are also +welcome on the developers list! You can find an overview of all Privoxy-related +mailing lists, including list archives, at: http://sourceforge.net/mail/? +group_id=11118.