There's a difference between using tools like Piwik (which still burden the browser with additional HTTP requests), and logging the relevant data in the application or server code itself (Apache/nginx logs, or writing your own context aware logging code in your Django/Rails/whatever framework application).

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.

The GP was complaining that users still block Piwik and other self-hosted solutions. Of course they do. I'll block every single request I can, if it's not just fetching the content that I want.

Some developers and content providers complain that by blocking analytics services (including internally hosted ones) means they'll be left completely in the dark. This is wrong. They can always log visits through their web app code on the server side - they'll have the benefit of complete request context access ("Is the user logged in?", "Is their account in credit?", "Did they buy this item at some point in the past?") but simply won't be able to correlate this data with other websites logs (a benefit to the users, from a privacy perspective).

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.