X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=README;h=548cc2faf9b288235c444a4d2e37a3d7958e3406;hp=c9835abbb9706aa1f5f6ba78b0b3ae5ac4e594ae;hb=21a2acc10c95913f50d72aa70815254a9a7702ef;hpb=bbbe3211c8fdbca92bb5d9c452ce720b3d349895

diff --git a/README b/README
index c9835abb..548cc2fa 100644
--- a/README
+++ b/README
@@ -32,7 +32,7 @@
  *
  *********************************************************************/
 
-This README is included with Privoxy 3.0.22. See http://www.privoxy.org/ for
+This README is included with Privoxy 3.0.23. See http://www.privoxy.org/ for
 more information. The current code maturity level is "stable".
 
 -------------------------------------------------------------------------------
@@ -230,11 +230,8 @@ understanding actions, and action debugging.
 
 6.2. 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.
+All users are welcome to discuss their issues on the users mailing list, where
+the developers also hang around.
 
 Please don't send private support requests to individual Privoxy developers,
 either use the mailing lists or the support trackers.
@@ -278,21 +275,14 @@ 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.
-
 -------------------------------------------------------------------------------
 
 6.3.2. Reporting Bugs
 
-Please report bugs that aren't security issues through our bug tracker: 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. If already
-submitted, please feel free to add any info to the original report that might
-help to solve the issue.
+Before reporting bugs, please make sure that the bug has not already been
+submitted and observe the additional hints at the top of the submit form. If
+already submitted, please feel free to add any info to the original report that
+might help to solve the issue.
 
 -------------------------------------------------------------------------------
 
@@ -308,15 +298,7 @@ to the developer list to request a status update.
 
 -------------------------------------------------------------------------------
 
-6.5. Request New Features
-
-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.6. Mailing Lists
+6.5. Mailing Lists
 
 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
@@ -326,3 +308,12 @@ 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.
 
+-------------------------------------------------------------------------------
+
+6.6. SourceForge support trackers
+
+The SourceForge support trackers may be used as well, but have various
+technical problems that are unlikely to be fixed anytime soon. If you don't get
+a timely response, please try the mailing list as well. While it's hosted at
+SourceForge as well, it usually works as expected.
+