Guest wrote:@ Tom T.
i had tried 0.0.0.0,255.255.255.0,& others.none of them worked.
Did you read the link, "Then please see Editing HOSTS away from 127.0.0.1 for the quick-and-easy way to do this."
As noted there, after changing all the 127.x to (whatever else) you MUST reset the first entry to
which MUST ALWAYS be the first entry.
I'm sorry to have asked you to spend a couple of minutes reading that post, but it gets tiring typing the same thing 100 times each time any of 100 users asks the same question. This is why there are links, stickies, FAQ, etc. (No, I don't get paid by the hour, or it wouldn't matter. Actually, I don't get paid at all. The entire team is part-time, unpaid volunteers, donating however much of their precious spare time is left over after making a living, family/friends, having a Real Life, recreation, sleeping, eating, etc.)
I expect that not resetting localhost after editing is what broke your HOSTS before.
just as i thought,127.0.0.1 is better,because it is considered an industry standard.
Here I am
quoting Giorgio literally, as I normally wouldn't use such language:
Giorgio Maone wrote:Eat shit! One billion flies can’t be wrong.
A little more detail:
Giorgio Maone wrote:Who uses 127.0.0.1 for adblocking did not put enough thought into his business.
There’s no “industry standard” about hosts file used as a poor man adblocker, which is a hack at best.
There are IETF’s Networking Group RFCs (which are not standards either, but are the specification which the internet is built on and are much more authoritative than Microsoft itself, let alone any MVP): according RFC3330, networking, which say “127.0.0.1″ is the address of the loopback interface, where you can actually bind a web server, while “0.0.0.0″ is an alias for “all the network interfaces on this hosts”, and it’s used almost exclusively as a placeholder for server binding purposes. These designations don’t hint (or are even compatible) with any adblocking purpose.
That said, any IPv4 “address” whose rightmost byte is 0 is practically invalid as a destination, therefore I suggested 255.255.255.0 initially because the “0.0.0.0″ network is a local network anyway and caught by ABE, but at this moment (in current NoScript beta) “0.0.0.0″ should be equally good since invalid addresses like this are properly recognized.
as therube has confirmed cnet is riddled with adlog.com.com.(could the factor be that you are using a different ff version!?)
It was that my Hosts file was blocking them all. I can remove that, using a default Hosts file, and try to reproduce, but it doesn't sound as though you're interested:
look,we are dancing around this issue.adlog never used to get through.if Giorgio Maone wants to look into it,fine.if not,then that's the end of this.(i really don't see the point in discussing this further.)
If you are truly interested in further investigation, let me know, and I'll be happy to remove the Hosts blocking, and see what happens.
If not, not.
ETA:
You're concerned about an ad getting through, but not concerned about using a very obsolete Firefox 8.0, which has a number of CRITICAL security flaws, as per the security bulletins for 9.x, 10.x, and 11.0?
Fx 3.6.28 is still supported for security and stability issues. Fx 8.0 hasn't been, for quite a while. NoScript (or anything else) cannot guarantee to protect you from every flaw in the browser itself.