11. Contacting the Developers, Bug Reporting and Feature Requests

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:

11.1. Get Support

For casual users, our support forum at SourceForge is probably best suited: 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.

Please don't sent private support requests to individual Privoxy developers, either use the mailing lists or the support trackers.

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 or one of its features, your message may be accidentally discarded as spam.

If you aren't subscribed, you should therefore spend a few seconds to come up with a proper subject. Additionally you should make it clear that you want to get CC'd. Otherwise some responses will be directed to the mailing list only, and you won't see them.

11.2. Reporting Problems

"Problems" for our purposes, come in two forms:

11.2.1. Reporting Ads or Other Configuration Problems

Please send feedback on ads that slipped through, innocent images that were blocked, sites that don't work properly, and other configuration related problem of default.action file, to http://sourceforge.net/tracker/?group_id=11118&atid=460288, the Actions File Tracker.

New, improved default.action files may occasionally be made available based on your feedback. These will be announced on the ijbswa-announce list and available from our the files section of our project page.

11.2.2. Reporting Bugs

Please report all bugs through our bug tracker: http://sourceforge.net/tracker/?group_id=11118&atid=111118.

Before doing so, please make sure that the b/sor>  Ralf Horstmann
 Stefan Huehner
 Peter Hyman
 Derek Jennings
 Petr Kadlec
 David Laight
 Bert van Leeuwen
 Don Libes
 Paul Lieverse
 Toby Lyward
 Wil Mahan
 Jindrich Makovicka
 Francois Marier
 David Mediavilla
 Raphael Moll
 Amuro Namie
 Adam Piggott
 Petr Písar
 Dan Price
 Roberto Ragusa
 Félix Rauch
 Maynard Riley
 Chung-chieh Shan
 Spinor S.
 Bart Schelstraete
 Oliver Stoeneberg
 Peter Thoenen
 Martin Thomas
 Bobby G. Vinyard
 Jochen Voss
 Glenn Washburn
 Song Weijia
 Jörg Weinmann
 Darren Wiebe
 Anduin Withers
 Oliver Yeoh
 Jamie Zawinski

Privoxy is based in part on code originally developed by Junkbusters Corp. and Anonymous Coders.

Privoxy heavily relies on Philip Hazel's PCRE.

The code to filter compressed content makes use of zlib which is written by Jean-loup Gailly and Mark Adler.

On systems that lack snprintf(), Privoxy is using a version written by Mark Martinec. On systems that lack strptime(), Privoxy is using the one from the GNU C Library written by Ulrich Drepper.

./usr/share/doc/privoxy/user-manual/contact.html0000644000000000000000000003061411374466326020703 0ustar rootroot Contacting the Developers, Bug Reporting and Feature Requests

11. Contacting the Developers, Bug Reporting and Feature Requests

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:

11.1. Get Support

For casual users, our support forum at SourceForge is probably best suited: 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.

Please don't sent private support requests to individual Privoxy developers, either use the mailing lists or the support trackers.

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 or one of its features, your message may be accidentally discarded as spam.

If you aren't subscribed, you should therefore spend a few seconds to come up with a proper subject. Additionally you should make it clear that you want to get CC'd. Otherwise some responses will be directed to the mailing list only, and you won't see them.

11.2. Reporting Problems

"Problems" for our purposes, come in two forms:

  • Configuration issues, such as ads that slip through, or sites that don't function properly due to one Privoxy "action" or another being turned "on".

  • "Bugs" in the programming code that makes up Privoxy, such as that might cause a crash.

11.2.1. Reporting Ads or Other Configuration Problems

Please send feedback on ads that slipped through, innocent images that were blocked, sites that don't work properly, and other configuration related problem of default.action file, to http://sourceforge.net/tracker/?group_id=11118&atid=460288, the Actions File Tracker.

New, improved default.action files may occasionally be made available based on your feedback. These will be announced on the