News for hackers. Stuff that matters.
Re:Deconstructing Google’s excuses on tracking protection by gregdoesit on Friday August 23, 2019 @01:40PM (#20780234)
>This isn’t the first time that Google has used disingenuous arguments to suggest that a privacy protection will backfire. We’re calling this move privacy gaslighting, because it’s an attempt to persuade users and policymakers that an obvious privacy protection—already adopted by Google’s competitors—isn’t actually a privacy protection.

Exactly. Firefox and Safari have both implemented and keep improving the type of fingerprint protection that Google is throwing their hands in the air about.

This summary is a thorough response, pointing out just how ridiculous and meritless the original post[1] from Google was.

[1] https://www.blog.google/products/chrome/building-a-more-priv...

Re:Deconstructing Google’s excuses on tracking protection by shawnz on Friday August 23, 2019 @03:23PM (#20781549)
That original post was written by the same Justin Schuh who went on this ridiculous tirade on twitter claiming he headed the manifest v3 adblocker neutering changes for privacy reasons: https://twitter.com/justinschuh/status/1134092257190064128

Of course it's not possible that this is true since the observational capabilities of the API are explicitly not being deprecated, only the content blocking capabilities. In other official posts they have claimed that the real "justification" is for performance reasons, which I think is equally nonsense.

Re:Deconstructing Google’s excuses on tracking protection by magicalist on Friday August 23, 2019 @04:27PM (#20782225)
> the same Justin Schuh who went on this ridiculous tirade on twitter

can you link to the ridiculous tirade? Cause here's the text I see in full

> The sole motivation here is correcting major privacy and security deficiencies in the current system. I know, because I set that focus, and the team reports up through me. And here's a bit more context on the uBlock assertions. [link to other tweet]

> Honestly, all of the negative coverage here is because the team is doing all of this development in the open and engaging with the community. They're taking feedback and making significant changes in response. So the framing here is just not accurate.

Re:Deconstructing Google’s excuses on tracking protection by ngold on Saturday August 24, 2019 @01:54AM (#20785503)
Do the merits of his claims hold true? Then I don't care if it's written by a guppy fish with I'll intention. Truth is the standard. Not the writer.
Re:Deconstructing Google’s excuses on tracking protection by giovannibajo1 on Saturday August 24, 2019 @07:55AM (#20786622)
Depends on your point of view. Chrome is going to use the same architecture that Safari has had for a few years (on iOS and Mac): data-driven content blocking, where rules are declared by the extensions, and then read and implemented by the browser core with no JavaScript involved on each request.

Javascript-based content blocking is technically slower because you need to invoke V8 on all requests, and then it’s up to the extension to make sure that the JavaScript code is fast enough. It surely is more flexible (as you can do whatever you want in that javascript code) but it’s hard to beat a simpler, data-driven content blocking engine written in native code and integrated in the core.

Whether this difference in resources does have a concrete impact or not, remains to be seen. The fact that Apple Safari did it first makes me believe that there is some truth in the technical merit argument; surely Apple didn’t want to make sure their content blockers were ineffective, but was actually using the same approach as always: providing a possibly “weaker” but far more efficient implementation (compared to “de facto standards” on other platforms) to protect iOS resources usage.

Re:Deconstructing Google’s excuses on tracking protection by shawnz on Saturday August 24, 2019 @08:08AM (#20786667)
Here are some measurements from the Ghostery team which show that the impact of the non-declarative API can be extremely minimal, and maybe even negative if you consider the increased performance from the reduced ad load.

https://whotracks.me/blog/adblockers_performance_study.html

Re:Deconstructing Google’s excuses on tracking protection by EdwardDiego on Saturday August 24, 2019 @11:35AM (#20787722)
At the risk of being that guy who mistakes his anecdote for a datum, I've found the bigger ad-blocking extensions to have a larger performance impact - simply because they're evaluating large regex based block lists on each request.

That said - that's my choice, I don't have to use those extensions, but the gain is, to my mind, worth the pain. I really don't like the patronising "we know what's best for you" attitude of the Chrome developers - especially because what they came up with as being "best for us" is also best for Google.

Re:Deconstructing Google’s excuses on tracking protection by dannyw on Saturday August 24, 2019 @02:59AM (#20785711)
No. Ublock does not have a performance problem.
Re:Deconstructing Google’s excuses on tracking protection by daveevad on Saturday August 24, 2019 @02:22AM (#20785597)
> I know, because I set that focus

That's a dead give away to me that this person is not effective as it's a naked appeal to his own authority.

Re:Deconstructing Google’s excuses on tracking protection by ChrisCinelli on Friday August 23, 2019 @09:59PM (#20784694)
His job history may tell you another reason on his positions about the subject: https://www.linkedin.com/in/justinschuh/
Re:Deconstructing Google’s excuses on tracking protection by hellcow on Friday August 23, 2019 @10:34PM (#20784840)
TIL the engineering director for Chrome comes from the NSA and CIA. Surely he cares deeply about everyone's privacy now, though...

As for me, I'll use Firefox.

Re:Deconstructing Google’s excuses on tracking protection by sterlind on Friday August 23, 2019 @11:00PM (#20784940)
Over a decade of military and then offensive CNE work, a quick tour around the private sector and then a decade of leading Chrome. I guess Chrome had a ton of security issues early on? I can't really think why they'd pick someone like this for directing Chrome and not Chrome security specifically. Even picking him for his contacts doesn't make sense - it's a free product, not much in the way of government contracts to land. And from a "mole" perspective, it'd make more sense to go to Project Zero anyway.

Also, genuine question: isn't it hard to go private sector if most of your resume is redacted? How do you convince employers that you're talented?

Re:Deconstructing Google’s excuses on tracking protection by CydeWeys on Saturday August 24, 2019 @10:39AM (#20787358)
A lot of the time (most of the time), you end up in a particular specialty by career accident, not because you're genuinely excellent at that and only that, and not good at related adjacent things.
Re:Deconstructing Google’s excuses on tracking protection by lightedman on Saturday August 24, 2019 @01:02AM (#20785333)
You take the test which YC people fail to provide.

One that tests integrity along with diligence and capability.

Re:Deconstructing Google’s excuses on tracking protection by Hnrobert42 on Saturday August 24, 2019 @10:19AM (#20787256)
There are some who work for those organizations that care passionately about civil liberties and work hard to preserve them while still carrying out necessary functions of government.
Re:Deconstructing Google’s excuses on tracking protection by Nasrudith on Monday August 26, 2019 @11:39AM (#20800732)
"Necessary functions" like causing the Vietnam War, the Iraq War, installing dictatorships, training people behind such lovely ideas as "rape dogs", leading to Osama Bin Laden, snooping on everyone while failing to stop attacks they were outright told about.
Re:Deconstructing Google’s excuses on tracking protection by Hnrobert42 on Tuesday August 27, 2019 @04:36AM (#20807421)
No. Not like those.
Re:Deconstructing Google’s excuses on tracking protection by weq on Monday August 26, 2019 @12:05AM (#20797396)
hahahahahahah yeh right.

You have 2 types of people in the any DoD. 0) the peons who do what they are told. 1) the ones who are bright, know the deal, speak when spoken too, and generally play their role. 2) the ones who are protecting their patch with a bunch of bureaucracy.

Those people who care about civil liberties belong in to (1). They unfortunately, have no real say. And when push comes to shove, (2) owns (1, 0) in every shape and form. At best, (1) goes and takes job with a contractor.

Either way, just because you leave your job, doesnt mean you have left your job. If your a (2), u have a network of resources at your disposal. And sometimes, its calculated.

A (2) will always be a (2). Even in retirement. Even if they take a new job. Their network will remain.

Re:Deconstructing Google’s excuses on tracking protection by staticassertion on Friday August 23, 2019 @03:51PM (#20781874)
Justin is a trustworthy guy and, while unfortunate, I believe the Chrome security team was acting in good faith with the manifest v3 changes.
Re:Deconstructing Google’s excuses on tracking protection by ocdtrekkie on Friday August 23, 2019 @04:03PM (#20781994)
We probably shouldn't refer to someone as "trustworthy" who is repeatedly demonstrated to be blatantly lying and spreading clear falsehoods.

As the parent stated, manifest v3 changes didn't hide any information from extensions (hence, by definition, not improving privacy), and independent studies completely discredit Justin's claims about the effectiveness of ad targeting.

Re:Deconstructing Google’s excuses on tracking protection by targonca on Friday August 23, 2019 @04:55PM (#20782458)
His employer considers him trustworthy.
Re:Deconstructing Google’s excuses on tracking protection by prepend on Friday August 23, 2019 @08:09PM (#20784122)
Just because your mom thinks you’re handsome doesn’t mean you’re handsome.
Re:Deconstructing Google’s excuses on tracking protection by sk5t on Friday August 23, 2019 @09:44PM (#20784614)
Trusted to advance his employer's interests, do you mean?
Re:Deconstructing Google’s excuses on tracking protection by staticassertion on Saturday August 24, 2019 @11:44AM (#20787785)
I have no affiliation with Google or Justin.
Re:Deconstructing Google’s excuses on tracking protection by nsuser3 on Friday August 23, 2019 @06:39PM (#20783422)
I'm not his employer (luckily).
Re:Deconstructing Google’s excuses on tracking protection by dan-robertson on Friday August 23, 2019 @04:31PM (#20782254)
There were two parts to the changes. One that stops the current system of ad-blockers requiring them to use a different url-filtering api (specifically one which denies them the ability to read the urls), and one that puts really tiny limits on that api.

I think the first change was in good faith and reasonable. Provided the filtering abilities are reasonable, it is good for privacy and performance (and it would make sense for eg Firefox to support this api too). (I think I would be happiest with an api that lets you write a pure (somehow enforced) js function from url to an action (eg block/allow/upgrade to https) and 4 bits of data).

Although obviously it is unfortunate if it stops various good extensions from working well.

For the second change, I can’t decide. It could be that they were made deliberately small, or it could be that they didn’t really know what appropriate size limits would be and picked limits which were way too small.

Re:Deconstructing Google’s excuses on tracking protection by plorkyeran on Friday August 23, 2019 @08:45PM (#20784332)
No, they did not deny ad blockers the ability to read the URLs. They removed the ability to modify requests via the webRequest API, but left in the functionality for observing all requests made.
Re:Deconstructing Google’s excuses on tracking protection by shawnz on Friday August 23, 2019 @04:49PM (#20782412)
The limits aren't the only problem -- forcing everyone to use only the declarative API restricts the ability of adblocker vendors to develop new techniques for blocking different kinds of ads or privacy threats.
Re:Deconstructing Google’s excuses on tracking protection by dan-robertson on Friday August 23, 2019 @07:08PM (#20783660)
I agree that there are good reasons to want something less declarative but I claim that only allowing declarative rules is a reasonable bona fide choice from a security or privacy perspective. In particular if there were no question of motives, I think there would be far fewer complaints about this system being implemented. Indeed Apple’s system for mobile url filtering works like this and though some people complained about the lack of expressivity I didn’t see any complaints that it was some kind of conspiracy to sell ads.
Re:Deconstructing Google’s excuses on tracking protection by tsimionescu on Saturday August 24, 2019 @01:57AM (#20785516)
You keep missing the fact that there is no security/privacy advantage to what Google did, since the API for an extension to see every URL being accessed and use it in arbitrary ways still exists. They only removed the part where the extension could block that request from happening.
Re:Deconstructing Google’s excuses on tracking protection by SpicyLemonZest on Saturday August 24, 2019 @01:15PM (#20788361)
Selective request blocking has huge security implications. In many ways it's a similar attack surface to arbitrarily rewriting the content. (Imagine making some charges to your credit card, then blocking the request that lists card charges on your bank's website.)
Re:Deconstructing Google’s excuses on tracking protection by zwaps on Sunday August 25, 2019 @11:56AM (#20793628)
How long until we find out that Google adservers and tracking can not be blocked in the new API?

Who really thinks a whole professional team of developers goes and neuters adblockers for nothing?

Let us not be naive.

Re:Deconstructing Google’s excuses on tracking protection by rndgermandude on Friday August 23, 2019 @06:23PM (#20783289)
They didn't even try to solve it.

It took me less than 2mins of thinking (and I am hardly the smartest guy ever) about it to figure out that you can solve the potential privacy hazard that webRequest poses (extensions siphoning off request data) by introducing a special kind of content script, let's call it a request-script, that is input-only/one-way-communication except for a limited set of request manipulation and only when asked by the browser. Such as blocking requests. Of course, the devil is in the details here of what to allow and not allow.

The input-only nature still allows for it to be feed new/updates instructions, and it being a script it can still implement rules that cannot be implemented with a fixed rule list like google proposes. But it cannot make web requests and exfiltrate data like that, it cannot communicate back to the host extension and exfiltrate that like that, it cannot exfiltrate data, period. It only ever is allowed to perform certain (not all) request modifications and only when asked by the browser itself.

That leaves the "performance issues" google claims are a major problem. And indeed, there is a chance a misbehaving extension might obliterate performance. But you can do a lot of things in this space, too. "You" are the browser after all and any extension or any request script is at the mercy of what you're allowing it to do anyway. A low hanging fruit here would be to enforce that a request-script has to give an answer in a sane amount of time. Or warn users when an extension slows down requests too much.

And ultimately users will decide if a e.g. 100ms delay for each request is preferable over downloading a few megabytes of video ads for them or not. That is if google was really interested in protecting their users and improving their experience and did not have other motives...

Re:Deconstructing Google’s excuses on tracking protection by vengefulduck on Friday August 23, 2019 @10:10PM (#20784741)
Except the extension could just inject a script into the webpage and exfiltrate data that way.
Re:Deconstructing Google’s excuses on tracking protection by rndgermandude on Saturday August 24, 2019 @12:49AM (#20785293)
That requires some different permissions to the webRequest permission in question.

But yeah, a bad actor would probably just switch away from webRequest to <all_urls> + webNavigation permissions and siphon off data with content scripts. So google's argument that is is a privacy issue and thus they just HAVE TO cripple their webRequest APIs doesn't get any better.

Re:Deconstructing Google’s excuses on tracking protection by shawnz on Saturday August 24, 2019 @08:01AM (#20786643)
That is still possible with Chrome's new declarative model too, so the parent's idea is strictly an improvement.
Re:Deconstructing Google’s excuses on tracking protection by sfink on Tuesday August 27, 2019 @04:46PM (#20814256)
Blocking is itself a communications channel. You have some data to exfiltrate from extension to server. The page embeds a bunch of URLs to your ad server, you selectively block based on the data to exfiltrate, the server gets 1 bit per URL.

Any additional blocking capabilities (reordering, delaying, selective header stripping) increase the number of bits.

Re:Deconstructing Google’s excuses on tracking protection by tbodt on Saturday August 24, 2019 @02:48AM (#20785670)
> 100ms delay for each request

NOPE

Re:Deconstructing Google’s excuses on tracking protection by luckylion on Saturday August 24, 2019 @06:47AM (#20786432)
That was an example - it's actually more like one or two ms.
Re:Deconstructing Google’s excuses on tracking protection by JohnFen on Friday August 23, 2019 @05:59PM (#20783107)
His argument just doesn't hold up, though, so I have a hard time thinking that it's anything more than a sales job.
Re:Deconstructing Google’s excuses on tracking protection by tareqak on Friday August 23, 2019 @05:16PM (#20782666)
Isn't that Google blog article completely ignoring the fact that Google implementing tracking protection would hurt their ability to maintain marketplace dominance in one domain (66%+ of web browsers) in order to further maintain and entrench Google's dominance and profitability in yet another (web advertising), and therefore anti-competitive [0][1]?

I can completely understand that the software engineers working on Chrome are separate from the ones working on Ads, but ignoring that conflict interest that is extremely obvious to some outsiders reduces how seriously these arguments can be taken by this group of people. I think Google needs to do more to highlight that their technical choices in Chrome and other Google products and services does not advantage their Ad business if that is truly the case.

[0] https://www.netmarketshare.com/browser-market-share.aspx

[1] https://www.statista.com/statistics/193530/market-share-of-n...

Update: reworded and added a bit more.

Re:Deconstructing Google’s excuses on tracking protection by xvector on Friday August 23, 2019 @02:02PM (#20780508)
I am honestly surprised at how ridiculous Google’s original blog post was. Zero nuance.
Re:Deconstructing Google’s excuses on tracking protection by lowdose on Friday August 23, 2019 @03:15PM (#20781449)
It is double speak.
Re:Deconstructing Google’s excuses on tracking protection by dialtone on Friday August 23, 2019 @02:03PM (#20780522)
You are aware that Google has vowed to actively fight any sort of fingerprinting right? https://techcrunch.com/2019/05/07/googles-chrome-will-soon-g...
Re:Deconstructing Google’s excuses on tracking protection by magashna on Friday August 23, 2019 @02:13PM (#20780639)
"Don't be evil" they said, until it became inconvenient.

You can't take Google at their word because their word doesn't mean much. Especially when those vows directly contradict their main source of revenue, targeted ads.

Re:Deconstructing Google’s excuses on tracking protection by vezycash on Friday August 23, 2019 @05:12PM (#20782632)
“It is difficult to get a man to understand something, when his salary depends on his not understanding it.” ― Upton Sinclair
Re:Deconstructing Google’s excuses on tracking protection by adam12 on Friday August 23, 2019 @02:21PM (#20780750)
I loved Google back in 2005. It's sad to see what it has become.
Re:Deconstructing Google’s excuses on tracking protection by airstrike on Friday August 23, 2019 @03:06PM (#20781350)
I still loved it as late as 2008... remember this?

http://blogoscoped.com/google-chrome/1

Re:Deconstructing Google’s excuses on tracking protection by SilasX on Friday August 23, 2019 @02:21PM (#20780754)
To borrow from Tony Stark: And I vowed to stop eating dairy, but then they named a Ben & Jerry's flavor after me, so ...

Or Google's equivalent would be, "Then we realized there was money in it, so ..."

Re:Deconstructing Google’s excuses on tracking protection by ocdtrekkie on Friday August 23, 2019 @02:26PM (#20780816)
I didn't remember this line. III Avengers 14:53, apparently.
Re:Deconstructing Google’s excuses on tracking protection by SilasX on Friday August 23, 2019 @02:44PM (#20781046)
You mean Infinity War? I'd never heard it referred to as Avengers 3, although I guess it's the third Avengers-branded one. And I edited the actual quote to include "vow"; the original is, "And I swore off dairy, but then Ben and Jerry’s named a flavor after me, so…".
Re:Deconstructing Google’s excuses on tracking protection by ocdtrekkie on Friday August 23, 2019 @03:25PM (#20781579)
https://seanlennaerts.github.io/mcuverse/ is now the best way to reference MCU lines.
Re:Deconstructing Google’s excuses on tracking protection by wpietri on Friday August 23, 2019 @06:21PM (#20783267)
That is a delight. For those who haven't seen it, its title is "MCU Bible Verse", and it's a fast searchable list of quotes from the Marvel movies with references done in Bible style.
Re:Deconstructing Google’s excuses on tracking protection by Nicksil on Friday August 23, 2019 @02:10PM (#20780607)
The article you linked has Google stating they're planning, over the next few years, to add restrictions to the way fingerprinting is executed. Nothing mentions Google vowing to fight any sort of fingerprinting.
Re:Deconstructing Google’s excuses on tracking protection by kube-system on Friday August 23, 2019 @02:15PM (#20780670)
Yes, we're aware. The entire article linked in the OP is a direct response to Google's claims about fighting fingerprinting. The argument made by the Princeton researchers here is that Google's claims are not likely to result in good user privacy.
Re:Deconstructing Google’s excuses on tracking protection by taurath on Friday August 23, 2019 @02:08PM (#20780579)
They’re adding an option, knowing full well that 95% of users will never even think to look in the menu.
[dead]
Re:Deconstructing Google’s excuses on tracking protection by clairity on Friday August 23, 2019 @03:18PM (#20781501)
it's useful to know alliances that can cause insider bias, but the parent comment was adding relevant, mostly unbiased, and industry-knowledgeable information that should be encouraged rather than discouraged here.

and such a tool would ironically be a tracker (as others have noted).

Re:Deconstructing Google’s excuses on tracking protection by Crosseye_Jack on Friday August 23, 2019 @03:05PM (#20781335)
How would you monitor anon’s?

I know let’s build a tracking network (or join one, let’s say google as they are pretty large) and use that info to work out of their is a conflict of interest or not.

If said comment came from anyone else would it of been dismissed as quickly? Ok it’s Google so prob yes :-p

Re:Deconstructing Google’s excuses on tracking protection by manigandham on Friday August 23, 2019 @03:42PM (#20781780)
A better way is let the content speak for itself instead of relying on the person's identity.
Re:Deconstructing Google’s excuses on tracking protection by Liquix on Friday August 23, 2019 @02:53PM (#20781181)
Great catch + novel idea. But how would the tool distinguish between those sharing their legitimate controversial opinions (everyone has a right to free speech, no matter how 'brainwashed') vs. malicious active derailing?
Re:Deconstructing Google’s excuses on tracking protection by acollins1331 on Friday August 23, 2019 @02:59PM (#20781263)
Just knowing that the person is the CTO of adroll is enough. Let them speak their piece but it's basically a "this comment was paid for by" disclaimer.
Re:Deconstructing Google’s excuses on tracking protection by pvg on Friday August 23, 2019 @03:01PM (#20781297)
It would be against the rules of the site which disallow this kind of insinuation whether it's automated or not.
Re:Deconstructing Google’s excuses on tracking protection by dredmorbius on Friday August 23, 2019 @03:34PM (#20781691)
Evidence-based demonstration is not insinuation.

How HN decides to address that is a separate matter.

Re:Deconstructing Google’s excuses on tracking protection by pvg on Friday August 23, 2019 @03:38PM (#20781724)
There is nothing 'evidence based' here. There is nothing wrong with the comment, no evidence it is an attempt to 'discredit valid arguments or derail conversation'. That's just a completely baseless accusation and, again, the site guidelines ask people not to do that. The user's affiliation is listed right in their profile, to boot.

[Edit: mistook you for the original commenter and fixed that up]