+</sect2>
+
+
+<sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
+from the old <application>Junkbuster?</application></title>
+<para>
+ <application>Privoxy</application> picks up where
+ <application>Junkbuster</application> left off. All the old features remain.
+ The new <application>Privoxy</application> still blocks ads and banners,
+ still manages cookies, and still helps protect your privacy. But, these are
+ all enhanced, and many new features have been added, all in the same vein.
+ </para>
+ <para>
+ The configuration has changed significantly as well. This is something that
+ users will notice right off the bat. The <quote>blocklist</quote> file does
+ not exist any more. This is replaced by <quote>actions</quote> files, such
+ as <filename>default.actions</filename>. This is where most of the per site
+ configuration is now.
+ </para>
+</sect2>
+
+<sect2 renderas="sect3" id="features"><title>What are some of the new features?</title>
+<!--
+ Include newfeatures.sgml
+-->
+&newfeatures;
+
+</sect2>
+
+<sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
+<application>Privoxy</application> work? </title>
+ <para>
+ When you connect to a web site with <application>Privoxy</application>,
+ you are really connecting to your locally running version of
+ <application>Privoxy</application>. <application>Privoxy</application>
+ intercepts your requests for the web page, and relays that to the
+ <quote>real</quote> web site. The web site sends the HTTP data stream
+ back to <application>Privoxy</application>, where
+ <application>Privoxy</application> can work its magic before it
+ relays this data back to your web browser.
+ </para>
+
+ <para>
+ Since <application>Privoxy</application> sits between you and the
+ WWW, it is in a position to intercept and completely manage all web traffic and
+ HTTP content before it gets to your browser.
+ <application>Privoxy</application> uses various programming methods to do
+ this, all of which is under your control via the various configuration
+ files and options.
+ </para>
+
+ <para>
+ There are many kinds of proxies. <application>Privoxy</application> best
+ fits the <quote>filtering proxy</quote> category.
+ </para>
+
+</sect2>
+
+
+<sect2 renderas="sect3">
+<title id="knows">How does <application>Privoxy</application> know what is
+an ad, and what is not?</title>
+<para>
+ <application>Privoxy</application> processes all the raw content of every
+ web page. So it reads everything on each page. It then compares this to the
+ rules as set up in the configuration files, and looks for any matches to
+ these rules. <application>Privoxy</application> makes heavy use of
+ <quote>regular expressions</quote>. (If you are not familiar with regular
+ expressions, it is explained briefly in <ulink
+ url="../user-manual/appendix.html">the user manual</ulink>.) Regular
+ expressions facilitate matching of one text string against another, using
+ wildcards to build complex patterns. So <application>Privoxy</application>
+ will typically look for URLs and other content that match certain key words
+ and expressions as defined in the configuration files. For instance a URL
+ that contains <quote>/banners</quote>, has a high probability of containing
+ ad banners, and thus would be a prime candidate to have a matching rule.
+</para>
+<para>
+ So <application>Privoxy</application> will look for these kinds of obvious
+ looking culprits. And also, will use lists of known organizations that
+ specialize in ads. Again, using complex patterns to match as many potential
+ combinations as possible since there tend to be many, many variations used by
+ advertisers, and new ones are being introduced all the time.
+</para>
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="mistakes">Can <application>Privoxy</application> make mistakes?
+This does not sound very scientific.</title>
+<para>
+ Actually, it's a black art ;-) And yes, it is always possible to have a broad rule
+ accidentally block something by mistake. There is a good chance you may run
+ into such a situation at some point. It is tricky writing rules to cover
+ every conceivable possibility, and not occasionally get false positives.
+</para>
+
+<para>
+ But this should not be a big concern since the
+ <application>Privoxy</application> configuration is very flexible, and
+ includes tools to help identify these types of situations so they can be
+ addressed as needed, allowing you to customize your installation.
+ (<link linkend="badsite">See the appendix below</link>.)
+</para>
+
+</sect2>
+
+
+<sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
+<application>Privoxy</application>. Why should I use
+<application>Privoxy</application> at all?</title>
+ <para>
+ Modern browsers do indeed have <emphasis>some</emphasis> of the same
+ functionality as <application>Privoxy</application>. Maybe this is
+ adequate for you. But <application>Privoxy</application> is much more
+ versatile and powerful, and can do a number of things that browsers just can't.
+ </para>
+ <para>
+ In addition, a proxy is good choice if you use multiple browsers, or
+ have a LAN with multiple computers. This way all the configuration
+ is in one place, and you don't have to maintain a similar configuration
+ for possibly many browsers.
+
+ </para>
+</sect2>
+
+
+
+<sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
+warranty? Registration?</title>
+ <para>
+ <application>Privoxy</application> is licensed under the
+ GNU General Public License (GPL). It is free to use, copy,
+ modify or distribute as you wish under the terms of this license.
+ Please see the
+<ulink url="../user-manual/copyright.html#HISTORY">user-manual</ulink> for
+ more information on the license and copyright.
+
+ </para>
+ <para>
+ There is no warranty of any kind, expressed, implied or otherwise. That is
+ something that would cost real money ;-) There is no registration either.
+ <application>Privoxy</application> really is <emphasis>free</emphasis>
+ in every respect!
+
+ </para>
+
+</sect2>
+
+<sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
+
+<sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
+<para>
+ We, of course, welcome donations and use the money for domain registering,
+ regular world-wide get-togethers (hahaha). Anyway, we'll soon describe the
+ process how to donate money to the team.
+</para>
+</sect3>
+
+<sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
+<para>
+ Well, helping the team is always a good idea. We welcome new developers,
+ RPM gurus or documentation makers. Simply get an account on sourceforge.net
+ and mail your id to the developer mailing list. Then read the
+ section Quickstart in the <ulink url="../developer-manual/quickstart.html">
+ Developer's Manual</ulink>.
+</para>
+<para>
+ Once we have added you to the team, you'll have write access to the CVS
+ repository, and together we'll find a suitable task for you.
+</para>
+</sect3>
+
+</sect2>
+