*
* Purpose : README file to give a short intro.
*
- * Copyright : Written by and Copyright (C) 2001-2010 the
+ * Copyright : Written by and Copyright (C) 2001-2011 the
* Privoxy team. http://www.privoxy.org/
*
* Based on the Internet Junkbuster originally written
- * by and Copyright (C) 1997 Anonymous Coders and
+ * by and Copyright (C) 1997 Anonymous Coders and
* Junkbusters Corporation. http://www.junkbusters.com
*
- * This program is free software; you can redistribute it
+ * This program is free software; you can redistribute it
* and/or modify it under the terms of the GNU General
* Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at
* The GNU General Public License should be included with
* this file. If not, you can view it at
* http://www.gnu.org/copyleft/gpl.html
- * or write to the Free Software Foundation, Inc.,
- * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
+ * or write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
* USA
*
*********************************************************************/
-This README is included with Privoxy 3.0.17. See http://www.privoxy.org/ for
+This README is included with Privoxy 3.0.19. See http://www.privoxy.org/ for
more information. The current code maturity level is "stable".
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-1. IMPORTANT CHANGES
+1. CHANGES
-November 2010, Privoxy 3.0.17 stable is released.
-
-This is mainly a bug-fix release for the previously released Privoxy 3.0.16
-stable. It contains fixes for two bugs that could cause connections to appear
-to hang under certain circumstances when keep-alive support was enabled. Of
-course there are also a bunch of minor improvements. For details please see the
-"ChangeLog", the "What's New" section or the "Upgrader's Notes" in the User
-Manual.
+For a list of changes in this release, please have a look at the "ChangeLog",
+the "What's New" section or the "Upgrader's Notes" in the User Manual.
-------------------------------------------------------------------------------
Please don't sent private support requests to individual Privoxy developers,
either use the mailing lists or the support trackers.
+If you have to contact a Privoxy developer directly for other reasons, please
+send a real mail and do not bother with SourceForge's messaging system. Answers
+to SourceForge messages are usually bounced by SourceForge's mail server in
+which case the developer wasted time writing a response you don't get. From
+your point of view it will look like your message has been completely ignored,
+so this is frustrating for all parties involved.
+
Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
addresses have to be accepted manually by a moderator. This may cause a delay
of several days and if you use a subject that doesn't clearly mention Privoxy
debug 64 # debug regular expression filters
- If you using Privoxy 3.0.17 or later and suspect that it interprets the
+ If you are using Privoxy 3.0.17 or later and suspect that it interprets the
request or the response incorrectly, please enable
debug 32768 # log all data read from the network
and the ones entered by other "anonymous" users that may respond to your
request if they have the same problem or already found a solution. Note that
due to spam the trackers may not always allow to post without being logged into
-SourceForge. If that's the case you are still free to create a login that isn't
-directly linked to your name, though.
+SourceForge. If that's the case, you are still free to create a login that
+isn't directly linked to your name, though.
Please also check the status of your request a few days after submitting it, as
we may request additional information. If you use a SF id, you should
automatically get a mail when someone responds to your request. Please don't
-bother to add an email address when using the tracker, if you prefer to
+bother to add an email address when using the tracker. If you prefer to
communicate through email, just use one of the mailing lists directly.
+If you are new to reporting problems, you might be interested in How to Report
+Bugs Effectively.
+
The appendix of the Privoxy User Manual also has helpful information on
understanding actions, and action debugging.
If you prefer to communicate through email, instead of using a web interface,
feel free to use one of the mailing lists. To discuss issues that haven't been
-completely diagnosed, please use the Privoxy users list. Technically interested
-users and people who wish to contribute to the project are always 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
-.
+completely diagnosed yet, please use the Privoxy users list. Technically
+interested users and people who wish to contribute to the project are always
+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.
projects / privoxy.git / blobdiff