Michael [19.Nov.2008 16:07]:
On 10:05 Wed 19 Nov , Qian Qiao wrote:
...
In that case, isn't putting
127.0.0.1 ADDRESSES_TO_BE_BLOCKED
into /etc/hosts easier?
Or just set up a proxy.
No, perhaps not, considering the fact that there are so many sites with
pron. Maintaining such a massive hosts file is a disaster and worse still
the solution is not fullproof. But then, FWIW such problems seldom have
foolproof solutions.
Well, at least there is "mvps" [1] with a nice host-file, blocking
mostly ads, banners etc., which I use myself without much trouble.
While searching for a list of porn-sites to add to that list, I stumbled
upon BadHosts [2], which includes several hosts-files, one of them
entirely for porn-sites.
The sites listed there might get you started, but as noted by Qian Qiao
before, that list will never be complete or up-to-date. Besides, using
an anonymizer to reach one of those sites will get you there anyway. You
would have to block those, too.
My opinion: If children are to be "protected" from that kind of content,
seting up a public computer in a livingroom might be a better way (in
conjunction with a host-file maybe for those nasty ads). But as soon as
one starts blocking sites, the question will be where to stop.
JP
[1] http://www.mvps.org/winhelp2002/hosts.htm
[2] http://www.hostsfile.org/hosts.html
--
Time flies like the wind, but fruit flies like bananas.
