+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>General Information</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><H1
CLASS="SECT1"
><A
-NAME="GENERAL">1. General Information</H1
+NAME="GENERAL"
+>1. General Information</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="NEWJB">1.1. What is this new version of <SPAN
+NAME="NEWJB"
+>1.1. What is this new version of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> In the beginning, there was the
<A
CLASS="APPLICATION"
>Privoxy</SPAN
>, whose first
- stable release, 3.0, was released August, 2002.
+ stable version, 3.0, was released August, 2002.
</P
></DIV
><DIV
><H3
CLASS="SECT2"
><A
-NAME="AEN45">1.2. Why <SPAN
+NAME="AEN45"
+>1.2. Why <SPAN
CLASS="QUOTE"
>"Privoxy"</SPAN
->? Why a name change at all?</H3
+>? Why a name change at all?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
><P
> The developers also believed that there are so many changes from the original
code, that it was time to make a clean break from the past and make
- a name in their own right, especially now with the pending
- release of version 3.0.</P
+ a name in their own right.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="DIFFERS">1.3. How does <SPAN
+NAME="DIFFERS"
+>1.3. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> differ
from the old <SPAN
CLASS="APPLICATION"
>Junkbuster?</SPAN
+></A
></H3
><P
> <SPAN
><H3
CLASS="SECT2"
><A
-NAME="PROXYMORON">1.4. What is a <SPAN
+NAME="PROXYMORON"
+>1.4. What is a <SPAN
CLASS="QUOTE"
>"proxy"</SPAN
>? How does
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> work?</H3
+> work?</A
+></H3
><P
> A web proxy is a service, based on a software such as <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="WHATSANAD">1.5. How does <SPAN
+NAME="WHATSANAD"
+>1.5. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> know what is
-an ad, and what is not?</H3
+an ad, and what is not?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN136">1.6. Can <SPAN
+NAME="AEN136"
+>1.6. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> make mistakes?
-This does not sound very scientific.</H3
+This does not sound very scientific.</A
+></H3
><P
> Actually, it's a black art ;-) And yes, it is always possible to have a broad
- rule accidentally block or change something by mistake. There is a good chance
- you may run into such a situation at some point. It is tricky writing rules to
+ rule accidentally block or change something by mistake. You will almost surely
+ run into such situations at some point. It is tricky writing rules to
cover every conceivable possibility, and not occasionally get false positives.</P
><P
> But this should not be a big concern since the
><H3
CLASS="SECT2"
><A
-NAME="BROWSERS2">1.7. My browser does the same things as
+NAME="AEN143"
+>1.7. Will I have to configure <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ before I can use it?</A
+></H3
+><P
+> No, not really. The default installation should give you a good starting
+ point, and block <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>most</I
+></SPAN
+> unwanted content.</P
+><P
+> But you will certainly run into situations where there are false positives,
+ or ads not being blocked that you may not want to see. In these cases, you
+ would certainly benefit by customizing <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+>
+ configuration to more closely match your individual situation. And we would
+ encourage you to do this. This is where the real power of
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> lies!</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="BROWSERS2"
+>1.8. My browser does the same things as
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> at all?</H3
+> at all?</A
+></H3
><P
> Modern browsers do indeed have <SPAN
CLASS="emphasis"
><H3
CLASS="SECT2"
><A
-NAME="LICENSE">1.8. Is there is a license or fee? What about a
-warranty? Registration?</H3
+NAME="LICENSE"
+>1.9. Is there is a license or fee? What about a
+warranty? Registration?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="JOINTEAM">1.9. I would like to help you, what do I do?</H3
+NAME="JOINTEAM"
+>1.10. I would like to help you, what do I do?</A
+></H3
><DIV
CLASS="SECT3"
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-MONEY">1.9.1. Money Money Money</H4
+NAME="JOINTEAM-MONEY"
+>1.10.1. Money Money Money</A
+></H4
><P
> We, of course, welcome donations and could use money for domain registering,
buying software to test <SPAN
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-SOFTWARE">1.9.2. Software</H4
+NAME="JOINTEAM-SOFTWARE"
+>1.10.2. Software</A
+></H4
><P
> If you are a vendor of a web-related software like a browser, web server
or proxy, and would like us to ensure that <SPAN
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-WORK">1.9.3. You want to work with us?</H4
+NAME="JOINTEAM-WORK"
+>1.10.3. You want to work with us?</A
+></H4
><P
> Well, helping the team is always a good idea. We welcome new developers,
packaging gurus or documentation writers. Simply <A
projects / privoxy.git / blobdiff