4 trackers [added]

[yajr lazy]

These 4 web analytics organizations have trackers that get past ABP TF on my boxes; listed here now so I don’t forget. Their sites use their wares. Somebody feel free to figure out what from the sites below ABP TF needs to filter please, or when I have some more time I’ll do it.

http://www.3dlivestats.com/

http://admeta.com/

http://www.siteclarity.com/sc/

http://weborama.com/

-------------

http://datacore.sciflicks.com/12_monkey ... forget.wav

[rick752]

The delivery mechanism has to be found in the wild somewhere. It is possible that these may already be blocked if you are just going by the company domain name. Do you have any examples "in the wild"?

[rick752]

I went through these and did what I could find.

[yajr lazy]

What about---

http://img.jjill.com/images/js/hs_3_082207.js on http://www.jjill.com/jjillonline/index.aspx and

http://www.siteclarity.com/sc/hs_4.js on http://www.siteclarity.com/sc/

I note that SiteClarity, aka Harvest Solutions, is owned by CheetahMail, which is owned by Experian, the consumer credit reporting agency. Maybe now we can have all of our online interests tied to our credit reports, so that those pesky last bits of personal privacy can finally be done away with. . .just as soon as all crappers can be outfitted with webcams. Oh happy day!

[rick752]

Those 2 trackers are already blocked by generic strings.

[yajr lazy]

Those 2 trackers are already blocked by generic strings.

On my boxes those tracking scripts are not blocked by ABP TF. Also, on my boxes the web-bugs those scripts generate are not blocked by ABP TF either.

I note that my copy of ABP TF contains no rule blocking “hs_” anything. I also note that each of the relevant web-bug gif urls is composed in a way that gives rise to generic string mismatches, as far as I can tell.

Is there a difference in what we are seeing; is your browser is behind something, such as Norton's “anti-spam” add-on, that blocks certain web page single pixel gifs?

[rick752]

@jagr:

You aren't showing me anything for those that would warrant a blocking of those. You are only showing me a couple of first-party tracker examples that seem to be only used on that site itself (seeing those are the places you used as examples) .... one example being on the home page of that tracking service. The other one is a store's own tracker. Unless these scripts/images are used on other sites, I going to have to decline on these. Siteclarity's tracker is blocked on most sites. Unless you can show me that the "hs" request is used somewhere else, I can't see doing anything here. If I had to make a filter for every small site's own first-party-served counter, I would go out of my mind.