diff --git a/alternates/gambling-porn-social/readme.md b/alternates/gambling-porn-social/readme.md index fc7758821..56081a303 100644 --- 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 466de7355..58df2fe27 100644 --- 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 67aee83f6..02d41df20 100644 --- 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 0c2402cc5..b0a958df1 100644 --- 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 dff7a8ef7..39d8f3d44 100644 --- 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 0520a3518..811fb911e 100644 --- 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 d5cae6ac1..8a94952c6 100644 --- 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 4063ed1b2..6bd172074 100644 --- 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 e9579a691..fa0c2d504 100644 --- 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.