After thinking about all of that, I may have come up with a solution and would like a little feedback about it.
First:
I think that a simple community-made filter (all of us just adding what we considered to be "non-ads" to it would be the easiest way to do it). The list should end up fairly small and should be simple to make. It would be an optional filter for users to add.
Doing that would free up our regular filters so that we wouldn't have to deal with these annoyances and it would give users the choice of 'opting in' or not.
But now we have the problem of people who track hits through their sites with these stat companies .... how do you block something from putting a global cookie tracker on a computer but still allow people to get their hits?
....how about by blocking the script only in the stat counter, NOT the image

Most stat servers have 2 different items ... a script and an image.
A random example of typical stats tracking code on a page would usually be:
Code: Select all
http://www.stats.com/tracking.js
AND
http://www.stats.com/tracking.gif
Code: Select all
stats.com/$script
There would be no cookie set and the webmaster would still be able to record his site hits! Does it make sense?
*EDIT* The second part of the above post is an ignorant error of what I originally thought of how cookies were served. You can follow my "buffoonery" below in the "Rick, the Moron" posts
