|
Authored by: Anonymous on Friday, June 21 2013 @ 04:29 PM EDT |
Users can implement most of the do not track features themselves.
Mozilla just makes it easier. But, I have in my hosts file
*.facebook.com 127.0.0.1
which results in around half the pages I visit never stop "loading".
Obviously either the page, or Mr Zuckerberg, is waiting for an ACK
to complete the loop. The impression I get from this is that eg. the
NYT page does not belong to the NYT.
Now if Mozilla are gonna block all those UserAgent subparameters
in a Head request, this has to be A Good Thing. Google-analytics
can be end-run around by rigourous client-side cookie purging.
But for sites you sign-in to it's game over because the owner can
run a server-side database of user behaviour. Amazon do already.
They know about cookie purging. Other sites don't, and cajole
the user to use cookies to "improve their experience".
I would for some, but sorry I can't be bothered scripting exceptions.
[ Reply to This | Parent | # ]
|
|
|
|
|