Technical analysis of client identification mechanisms(chromium.org)
chromium.org
Technical analysis of client identification mechanisms
http://www.chromium.org/Home/chromium-security/client-identification-mechanisms
2 comments
Well, I think it honestly harkens back to Google's original "Don't be evil" motto. I think most of the people at Google want to "Do the right thing" as long as they keep their jobs.
They want to find the right balance, the problem is I think a large portion of Google has lost their way in that regard due to the need to make Google more money. If the volume isn't growing fast enough, they have to find newer...higher margin...options to grow.
They want to find the right balance, the problem is I think a large portion of Google has lost their way in that regard due to the need to make Google more money. If the volume isn't growing fast enough, they have to find newer...higher margin...options to grow.
After reading the post I don't think "they had lost their way" instead they are trying to find ways to help everyone involved.
Have you actually looked at how Google Analytics tracks users?
It's very straight forward, nothing like almost anything on this list.
It's very straight forward, nothing like almost anything on this list.
Like cookies? Like shared cookies if you opt-in?
I would imagine this has value not just to analytics. Deanonymization has a lot of value in curbing abuse. Privacy is of paramount value, though, so it's hard to reconcile. To me it's a dilemma.
This is a good guide to some of the ways that evercookie uses to live on even after you've cleared cookies:
https://github.com/samyk/evercookie
https://github.com/samyk/evercookie
Then again it kind of makes sense. Who better knows?