Do you block images, css, and other stuff that doesn't pertain to the content at hand?
> What I'm suggesting is that applications can completely unobtrusively log visitor data internally, without requiring the client to make additional requests. In the same way that ad networks could serve data through your own application backend (rather than being requested by the client), if the ad networks and advertisers could stomach losing access to cross site user data tracking.
Yeah if all you want is referrer, user agent, url requested, and ip. But what about other great information in help with making your site BETTER for your users, like screen size?
> As a user, there is absolutely no benefit to me whatsoever of your site knowing my age, income bracket, recent (off-site!) browsing history and interests. None. Ad networks, advertisers and content providers will benefit. I won't.
I find it strange given the demographics of HN that people still believe by me putting Pwiki on my site to gather analytics about my visitors, that somehow taps into your bank account to see your income, requests your tax documents, downloads your birth certificate and gives me a full list of your last 100 visited urls.
That data is only available if I somehow put a tracking pixel on as many sites as I can. Such as a 3rd party script.
So because of that I can see blocking Google Analytics, or 3rd party trackers, but what are you doing by blocking 1st party stuff like Pwiki other than giving a big fuck you to the website owner?