"First, large scale blocking of cookies undermine people’s privacy..."
Oh yeah, users and their privacy first!
"Second, blocking cookies without another way to deliver relevant ads significantly reduces publishers’ primary means of funding..."
Also we make less money when you do this... But users, privacy and synergy first!
I think the second point is the real issue for Google. But of course they care about users first! I feel cynical as hell, but the whole thing reads so slimy to me. Like a used-car salesman twisting an obvious negative into a positive. "That's not a giant rust hole, that's just to reduce weight for efficiency!"
That's because when you try to log into one of those, it tries to simultaneously log you into the other domains/Google products linked to your account and per-domain sandboxing prevents that.
My setup against tracking is as follows:
- Temporary Containers: Prevent cookie-based tracking
- ClearURLs: Prevent URL-based tracking, which Google and Amazon use everywhere
- VPN: Prevent IP-based tracking, to some degree
- uBlock Origin: Block adds and some nasty JavaScript
I find it quite hard to prevent fingerprinting. The privacy.resistFingerprinting in Firefox breaks tons of things. So does blocking JavaScript. And uMatrix is a bit time consuming to use, and not suited for inexperienced users.
Any alternatives considering aside from Tor Browser?
This will be an arms race and seems to be occurring over the course of decades. There will end up being extensions to regularize the timing of your keystrokes and mouseclicks because they give away your identity, VPNs will be integrated into the browser, anything to combat the information leakage.
.. and these users will be flagged as bots :) .. :(
In practical terms, the point is important. Even if Google doesn't change their behavior to find other ways to invade your privacy, there are lots of other companies whose financial incentives point solidly that direction.
With enough people standing to gain enough money, someone's going to cross that moral line. Is this cynical? Absolutely. Correct? Almost certainly. Is it something we should take seriously as a result? I think so, though obviously opinions may differ on the subject.
Few publishers are confident in their ability to jettison an targeted-advertising-based business model for an alternative model that produces similar financial results.
Issue is Google's third suggestion, "A per-first-party identity can only be associated with small amounts of cross-site information", is clearly advertiser-focused, not privacy-focused.
I hope all can rally around the partitioning concepts and leave the others behind.
[1]https://github.com/michaelkleber/privacy-model [2]https://webkit.org/blog/8828/intelligent-tracking-prevention...
The identity "Me while I'm visiting nytimes.com" is distinct from the identity "Me while visiting cnn.com".
To me, this means all client-triggered requests while my address bar ends in "nytimes.com" will have a distinct set of cookies that is only drawn from while I'm on nytimes.com.
I prefer a rules-based solution to an ML-based solution. ML is more opaque and it's harder for developers to know when their solution will run afoul of the classifier.
Are there significant compatibility problems this would cause?
Anyway, the reason we moved away from cookie partitioning is that many third party embeds got confused when presented with non-empty cookies, but ones that weren’t the user’s canonical cookie for that site. Bugs were reported to us by embed providers, including Google web properties. This is a bummer because partitioning is elegant and has been WebKit’s go to approach since 2013, when we partitioned all storage besides cookies (LocalStorage, the HTTP cache, etc). A move that, incidentally was opposed by Chrime Engineers back when we shared an engine code base, though they are coming around now.
(I should mention also that partitioning cookies made many social embeds stop working at all until we provided Storage Access API and got embed providers to adopt them, which is why ITP originally had a 24 hour user interaction exception. Fortunately the web has adapted now.)
I should also mention, WebKit ML solution is deterministic. It’s trained offline. And it doesn’t substitute for enforcement actions, it substitutes for a block list of known trackers, which other tracking prevention systems use. One downside of strict rule based systems is that it may allow malicious players to game the system. So there has to be an out for changing the rules or ratcheting up enforcement.
I do still wish the ML stuff weren't there, though. As a developer for a small company that's trying to become a big company (and develops on these boundaries), I fear we'll build something that works one day, but the next will be classified and the rules will change.
I'd rather have a policy that forces big and small sites to follow the same rules. Between storage access and link decoration detection, WebKit seems quite close to being able to detect cross-site tracking as it happens rather than via classifier, and I'd hope that could one day replace the ML component.
Seeing as Google doesn't engage in fingerprinting and are actively taking steps to block it[1], I don't think this is a fair characterization of Google's position.
[1]: https://blog.chromium.org/2019/05/improving-privacy-and-secu...
Google's position here is, "obviously you're going to have to let us track you some way, and our way (cookies) is better than fingerprinting." It's still blaming privacy-conscious users for the actions that advertisers have taken, because those unreasonable privacy-conscious people couldn't be content with just blocking some of the trackers.
There's an underlying tone to this article that reads as, "you all messed this up because you didn't just leave well enough alone. Now we'll come in and fix it, but you're gonna have to compromise with us when we do." From my perspective -- no, users didn't break anything. This isn't our fault, and we should be allowed to broadly block cookies without being tracked in more pervasive ways.
But, if it makes you feel better you can change a word in my characterization to read:
> "If y'all had just handed over your wallet when we asked, they wouldn't have had to hurt you. So really, this is your fault."
That seems like a 180 from their stance 2 years ago[1]. Their statement is low on details so I'll believe it when I see it. Right now the only browser with meaningful fingerprinting protection is tor browser/firefox.
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=49075
[1]: https://bugs.chromium.org/p/chromium/issues/list?q=component...
Naturally, blocking other companies' fingerprinting is important to their business model.
(There are some cases where identifiers are pulled in from other systems, but none of them can be used as the basis for unifying users.)
Analytics doesn't either, it uses regular cookies. (See sibling comments.)
I don't know why HN seems to be so stubborn about things like this. It's clear as day they fingerprint users, but seems like the majority of users here refuse to believe a corporation or government has done anything wrong unless they literally admit it in a press release.
GA isn't nearly as invasive as people think. The real problem is data being combined on the backed and correlated across websites by ad networks, not the analytics itself.
Edit: Worth a look if you're interested in what's being collected: https://developers.google.com/analytics/devguides/collection...
Unfortunately, that sounds exactly like the set of information that can be used to fingerprint users.
What would happen to fingerprinting in the case of "large scale disabling of Javascript"?
Even more, what would happen if there was large scale movement away from Chrome and other browsers with "features" that make fingerpinting possible?
But it would certainly be a lot easier to do all of that without Javascript.
The problem is that one of two things would happen:
A) the majority of web apps would move to native platforms, where fingerprinting resistance is even worse. That would include a good many news sites, even though most news sites aren't really web-apps, and don't need Javascript to operate. They'd still do it.
B) the majority of users would not use those browsers. We're playing a kind of weird game with fingerprinting right now -- we want to block it without breaking most websites. This is why adblocking is fantastic: it observably makes the web better to even an average user, so there's an incentive for users to adblock en-mass, and publishers can't really leave the web. Adblocking is a way to fight surveillance apparatuses without making sacrifices.
It's a tricky situation to be in, and there's a lot more that could be said about the merits of different strategies.
That being said, if you don't care about an en-mass policy, and you're just looking to increase your own privacy, it would definitely be a good idea right now to use something like UMatrix to disable at least 3rd-party Javascript by default. You'll have to do a lot of per-website tweaking, but if you're at all technical it's honestly not that bad.
At the same time, a lot of people don't understand what cookies actually do (the good things they do, I mean) and thus having them disabled by default will deepen their belief that they're only bad.
I'm not sure what I'd do if cookies were blocked by default. What an absolutely inconvenient reality that would be as a web developer. You'd have to embed a token in the page on each request, like WebForms, or something.
This is Google saying, "oh looks like everyone else is doing things that hurt our business, so let's get everyone to work together on open standards, where we can block or delay attempts that run counter to our business model".
"If y'all had just handed over your wallet when we asked, we wouldn't have had to hurt you. So really, this is your fault."
More seriously, what Google is saying here is that privacy can't be mainstream. It's no different from the arguments that advertisers gave when they rejected DNT. They're willing to let a few privacy-minded people avoid being tracked, as long as that group never becomes a majority. But it was never their plan to get rid of tracking, every compromise they ever offered had the catch, "as long as it doesn't affect our bottom line."
It's just another Equifax settlement. "Yeah we offered it, but we never assumed that so many of you would take it. Be reasonable."
Heck that. If you genuinely believe that people should have a choice about privacy, then you have to accept that maybe the majority of people will decide they don't want cookies. You have to take a step back and consider that browsers that block cookies by default are just reflecting what their users already widely want; people want their browsers to protect them from tracking by default, without configuration.You're not offering users a choice, you're just mad that you can't use dark patterns to make users unsafe-by-default.
This entire article is just insulting.