Blocking fetchback tracking..
Posted: Mon Sep 06, 2010 9:36 pm
Hi Giorgio Maone,
Well we all know here that we are being tracked all the while by stealth hidden ways e.g. via webbugs even after we have left the website in question (for instance take the so-called Fido server "fetchback"tracking). Interesting discussions to block them are to be found here: https://nodpi.org/forum/index.php/topic,673.0.html
An example for you. A controversial US online advertising company has turned to agency support to launch its services in the UK.
NebuAd analyses the websites people visit, so that it can deliver online advertising based on their interests.
Re the FAQ: http://w2.eff.org/Privacy/Marketing/web_bug.html
It means that the ads people encounter on the web can change according to previous websites they have visited....thats just it - they will be sending out adverts on post data "after the fact" that means after you already done what you wanted to do, so they be coming in last - not very good, is it? The real losers will be the companies that paid them for the ad to be served and us. the browser user, as our data will be sold on. So the fetchback tracker is the only party to get wiser from the deal and companies and users both loose out. You certainly do like or need to block such a tracker, won't you? These practices go hand in hand with tracking on parked websites for instance (tracking cookies).
Is it true that we can block this fetchback tracking by just generally blocking webbugs with the specific setting option in NoScript via :Options-Advanced, Forbid "Web Bugs"?
As there are also ways of fetchback tracking via iFrame which drops several cookies, then we have to block iFrames as well?
luntrus
Well we all know here that we are being tracked all the while by stealth hidden ways e.g. via webbugs even after we have left the website in question (for instance take the so-called Fido server "fetchback"tracking). Interesting discussions to block them are to be found here: https://nodpi.org/forum/index.php/topic,673.0.html
An example for you. A controversial US online advertising company has turned to agency support to launch its services in the UK.
NebuAd analyses the websites people visit, so that it can deliver online advertising based on their interests.
Re the FAQ: http://w2.eff.org/Privacy/Marketing/web_bug.html
It means that the ads people encounter on the web can change according to previous websites they have visited....thats just it - they will be sending out adverts on post data "after the fact" that means after you already done what you wanted to do, so they be coming in last - not very good, is it? The real losers will be the companies that paid them for the ad to be served and us. the browser user, as our data will be sold on. So the fetchback tracker is the only party to get wiser from the deal and companies and users both loose out. You certainly do like or need to block such a tracker, won't you? These practices go hand in hand with tracking on parked websites for instance (tracking cookies).
Is it true that we can block this fetchback tracking by just generally blocking webbugs with the specific setting option in NoScript via :Options-Advanced, Forbid "Web Bugs"?
As there are also ways of fetchback tracking via iFrame which drops several cookies, then we have to block iFrames as well?
luntrus