Better explanation of why we use the 0.0.0.0 address.

Just the readme_template.md file is changed.  All the other readme files in this commit are generated.

Closes Issue #68.

diff --git a/alternates/gambling-porn-social/readme.md b/alternates/gambling-porn-social/readme.md
index fc77588219ffa5f5bf351fa345fdfb96b5aa837e..56081a3037829a74295e8e3c5e19d2c0f2bae2a5 100644 (file)
--- a/alternates/gambling-porn-social/readme.md
+++ b/alternates/gambling-porn-social/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/alternates/gambling-porn/readme.md b/alternates/gambling-porn/readme.md
index 466de735501e104e52f87bad7dce829f71520d45..58df2fe27edb21cba88311d5af81217f94d67f48 100644 (file)
--- a/alternates/gambling-porn/readme.md
+++ b/alternates/gambling-porn/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/alternates/gambling-social/readme.md b/alternates/gambling-social/readme.md
index 67aee83f65d962e923f5c17a04d2bf1656c11eca..02d41df20a283ef123733dabb97d806403131443 100644 (file)
--- a/alternates/gambling-social/readme.md
+++ b/alternates/gambling-social/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/alternates/gambling/readme.md b/alternates/gambling/readme.md
index 0c2402cc5275b915a50f6cc8eeeb62d68d79e19b..b0a958df16e920115c507ddb89031b269881f866 100644 (file)
--- a/alternates/gambling/readme.md
+++ b/alternates/gambling/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/alternates/porn-social/readme.md b/alternates/porn-social/readme.md
index dff7a8ef7af12bf10e1700d2d7e39a8f7221cbe2..39d8f3d44ba3be83e425f17a8ca4f318eb8ea408 100644 (file)
--- a/alternates/porn-social/readme.md
+++ b/alternates/porn-social/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/alternates/porn/readme.md b/alternates/porn/readme.md
index 0520a3518b204d6c8147c85ab43e3cede8a5ae6d..811fb911e3a6211dc37fb1872e5f93d1149b9673 100644 (file)
--- a/alternates/porn/readme.md
+++ b/alternates/porn/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/alternates/social/readme.md b/alternates/social/readme.md
index d5cae6ac149a491e3199f8c7281ce82288c814d6..8a94952c6903eba95e3141b9f47a90c0effc982d 100644 (file)
--- a/alternates/social/readme.md
+++ b/alternates/social/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/readme.md b/readme.md
index 4063ed1b2669091cbf61b8310647bb1a0995d23d..6bd172074e35a57f766bc1904e9202acfaa6a76c 100644 (file)
--- a/readme.md
+++ b/readme.md
@@ -125,17 +125,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.

diff --git a/readme_template.md b/readme_template.md
index e9579a6912ea25cc2f297005016a9d14502479bd..fa0c2d5046ca97e0c9d46116ae130f21bd7f305d 100644 (file)
--- a/readme_template.md
+++ b/readme_template.md
@@ -117,17 +117,23 @@ For example, to nullify requests to some doubleclick.net servers, adding these l
 file will do it:
 
     # block doubleClick's servers
-    127.0.0.1 ad.ae.doubleclick.net
-    127.0.0.1 ad.ar.doubleclick.net
-    127.0.0.1 ad.at.doubleclick.net
-    127.0.0.1 ad.au.doubleclick.net
-    127.0.0.1 ad.be.doubleclick.net
+    0.0.0.0 ad.ae.doubleclick.net
+    0.0.0.0 ad.ar.doubleclick.net
+    0.0.0.0 ad.at.doubleclick.net
+    0.0.0.0 ad.au.doubleclick.net
+    0.0.0.0 ad.be.doubleclick.net
     # etc...
 
 
 ## We recommend using `0.0.0.0` instead of `127.0.0.1`
-Using `0.0.0.0` is faster because you don't have to wait for a timeout. It also does not interfere
-with a web server that may be running on the local PC.
+
+Traditionally most host files use `127.0.0.1`, the *loopback address*, to establish an IP connection to the local machine.
+
+We prefer to use ``0.0.0.0`, which is defined as a non-routable meta-address used to designate an invalid, unknown,
+or non applicable target.
+
+Using `0.0.0.0` is empirically faster, possibly because there's no wait for a timeout resolution. It also does not
+interfere with a web server that may be running on the local PC.
 
 ## Why not use just `0` instead of `0.0.0.0`?
 We tried that.  Using `0` doesn't work universally.