31 Aug
2020
31 Aug
'20
7:39 p.m.
On Monday 31 August 2020 07:22:53 Michael wrote:
Very cool. Thanks.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
{snip a bunch!}
Summary version! We keep saying the same thing and re-asking the same
questions. Boiling everyone’s [correct AFAIK] statements into a whole.
{Hopefully I didn’t miss anything!}
Brevity is the soul of something or other. Or so I've heard. Personally, I
believe we ought to give verbosity and prolixity a try, just to see how it
works out.
0.0.0.0 vs. 127.0.0.1
It doesn’t matter, both get served locally. [Paste both into a web
browser :) ]
AFAICT this is the convention now:
- Use 0.0.0.0 to block.
- Use 127.0.0.1 to connect to your local web server, proxy, or other local
port.
Why the historic use of 127.0.0.1 to block?
I don’t know, and do not take this as truth… It’s possible 0. didn’t exist
original and was added after 20??. Based on memory 127. was the only
number I ever saw in hosts files pre 2000-2005? (I ran the Linux Router
Project (LRP, the precursor to LEAF) through most of the 90s and early
00s.)
the two variants used in tandem -- for example,
you
mentioned "if you have a web server"? Maybe, then, it would be useful to
create a home version and a web server version.
No.
Pretty much both sets of entries would be needed at the same time. They
aren’t going to overlap.
Errata: Okay, in some bizarre circumstance where you want (hard to figure
out a need) the same exact address to be blocked in one instance and served
locally in another, then yeah, you’d need to list ‘swap.’
I believe Michael mentioned some kind of script?
this is the sniplet from rc.local:
# HOSTS-Datei mit Adblocker :-)
(
sleep 5m
cat > /etc/hosts << XXX
# insert your hostname here
127.0.0.1 localhost t61
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
XXX
wget http://winhelp2002.mvps.org/hosts.txt -O - 2>/dev/null | grep
^0.0.0.0 >> /etc/hosts ) &
This is essentially what the script I wrote does. It separates the logic
from the hosts entries so you can manage ‘# insert your hostname here’
easier, add custom blocks easier, and is a bit safer, but it’s the same.
I’ve attached it again.
PS: The block list I used (StevenBlack's) combines winhelp2002’s, Peter
Lowe's, and many other block lists into one, so scan it to see if it’s
already got any you want to add to the wget pulls.
Could/should I run both a hosts block list and Ad
Blocker?
Yes. They will both catch ‘nasty’ things the other won’t. Most noticeable
will be an Ad Blocker will catch self served ads on sites you want to
visit. And AFAIK most Ad Blocker lists (get paid to) whitelist Google ads,
which the hosts block list will catch.
Best All,
Michael
PS: If anyone does find another block list to add, send me the wget pull
link and I’ll finish the script to handle multiple combines.