Running the HTTP Debugging tool Fiddler under a browsing session is also a good way of getting a view of what goes on under the browser hood qua user tracking activities. I found a request by static.tradetracker.net/nl hosted by ti.tradetracker.nl
policyref: http://ti.tradetracker.nl/public/wc3/p3p.xml
Also found that it was blocked with this blocklist: http://dutchmega.nl/dutchblock/list.txt
Normally these issues are blocked by ABP+
Who among the users just think these tracking activities are benign and eventually will benefit the use of the Internet or who wants to block these requests?
I’m all for blocking as you can imagine. This said Fiddler is indeed a great tool >>> a great application for it is Chrome where ad blockers don’t really block ads…and you see (in fiddler) what goes on in the background. This said, I’ve read a few comments on Chrome extension pages, comments from users saying that Google was working on deep modifications of the API to allow the real blocking of ad servers (just a rumor so far…but plugins can already be blocked on a site per site basis already, a bit bugged but it’s there, so this can be used too). I know they don’t like the idea (@ Google ;D )…but they need the user base, and many come from Firefox, and they need to be convinced
Yes. my friend, we are spreading these ideas here. After the host sites blocking there’s now the ad-tracking blocking. There are quite some good reliable tools/extensions to achieve this - Fiddler detects, NoScript, RequestPolicy and ABP+ filters this out of the browser.
And what you really want to allow inside the browser should be just your decision, isn’t it?
