News for hackers. Stuff that matters.
Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Wednesday May 29, 2019 @09:52PM (#20047648)
Manifest V3 still supports ad blocking. I don't know why so many in this thread think it doesn't.
Re:Google to restrict modern ad blocking Chrome extensions t... by zwaps on Thursday May 30, 2019 @03:01AM (#20049007)
It does not allow blocking Google\any tracking and Google ads, essentially, and gives the Ad industry (and malware) a way to circumvent the blocker with modern tech, because it is a non smart ad blocker but a dumb filter list from 2002.

This is fully intended to give Google the ability to use sophisticated scripts to serve ads and track you despite blocking. Everything else Google says about this is bull!

They probably already have the tech set up. And that real blocking still works for Enterprisr customers is the nail in thr coffin.

If you care about a usable Web, STOP USING CHROME.

Google is has become the #1 anti user and anti freedom company. They want to make money from Ads and tracking, so dont think they will allow you to block ads.

Re:Google to restrict modern ad blocking Chrome extensions t... by rocqua on Thursday May 30, 2019 @03:46AM (#20049181)
> It does not allow blocking Google\any tracking and Google ads

As per the article, you can still use a rule set to block. Whilst undoubtably less powerful, I would expect that could still be used to block Google stuff.

Re:Google to restrict modern ad blocking Chrome extensions t... by zwaps on Thursday May 30, 2019 @05:18AM (#20049559)
Why would you expect that? It seems to me that Google does this precisely because they have tech to circumvrnt dumb- style list blocking, but not more advanced heuristics.
Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Thursday May 30, 2019 @08:42AM (#20050534)
>It does not allow blocking Google\any tracking and Google ads

Why not? Have you read the spec for chrome.declarativeNetRequest? Please substantiate your comment.

Re:Google to restrict modern ad blocking Chrome extensions t... by seangrant on Wednesday May 29, 2019 @09:59PM (#20047695)
Rule-based ad blocking limited to 30k, as stated in the article. That's why people are upset.
Re:Google to restrict modern ad blocking Chrome extensions t... by ehsankia on Thursday May 30, 2019 @12:28AM (#20048388)
Except that list really is just bloated with rules that don't do anything anymore.

> We measure how EasyList affects web browsing by applying EasyList to a sample of 10,000 websites. We find that 90.16% of the resource blocking rules in EasyList provide no benefit to users in common browsing scenarios.

[0] https://arxiv.org/pdf/1810.09160.pdf

They've also mentioned the possibility of tweaking the 30k limit.

Re:Google to restrict modern ad blocking Chrome extensions t... by danShumway on Thursday May 30, 2019 @01:16AM (#20048604)
> in common browsing scenarios.

Part of the point of an adblocker is to protect you in uncommon browsing scenarios. This is almost like saying that a malware list is bloated because some of the hashes its storing are uncommonly downloaded. Having as close to full coverage as possible is important.

It also opens up an attack vector for advertisers that they absolutely will exploit. With unlimited rules, there's no reason for ad networks not to use a few domains and serve their ads from a few sources. With a hard limit, there's a strong incentive for networks to collectively try and flood the lists with tons of different domains until we run out of room to include all of them.

> the possibility of tweaking the 30k limit.

This has been the number one complaint about the proposal from day one. If at this point the Chrome team still hasn't decided to tweak the limit, I just don't see how there's not gonna be any new argument past this point that anyone can make to convince them.

Re:Google to restrict modern ad blocking Chrome extensions t... by ehsankia on Thursday May 30, 2019 @01:29PM (#20053712)
Comparing it to a malware list is a bit extreme, isn't it? In one case, you actually get infected, in the other, you see one ad. Your next point about advertisers abusing it is a good one though.

I believe in the response, they said they are running benchmarks to see the performance hit, so they are definitely still looking at tweaking the limit.

Re:Google to restrict modern ad blocking Chrome extensions t... by danShumway on Thursday May 30, 2019 @05:25PM (#20056057)
I don't think the consequences are the same, but I do think the underlying idea is applicable.

Two things to keep in mind:

A) uBlock Origin doesn't just protect me from ads, it also protects me from many trackers. I'm in the (maybe minority, I don't know) camp that says that excessive tracking and de-anonymization attempts cause people tangible harm. They're not as drastic or as harmful as installing malware on my computer, but I put these practices in the same category as a malicious attack.

B) Under the most recent stats I've checked, Malvertising has almost surpassed general unsafe sites like porn/torrents as a source of consumer malware. Even Google Ads aren't immune from some of these attacks[0]. So for less computer-literate friends that I have, I consider a gimped adblocker to be a malware risk source.

But to your point, maybe a less emotionally charged comparison could be Chrome's automatic whitelist for autoplaying videos. Nobody is going to die if a video autoplays on their tablet, but at a fundamental level the point of blocking autoplay is to actually block it, everywhere. Not to block some of it. People didn't want Google trying to guess which video sites were the most annoying, they just wanted Google to turn off autoplay.

In the same sense, if someone installs an extension that says it's going to block ads and trackers, I don't think it's unreasonable for a consumer to want it to block all of the ads (or at least as many as is possible to detect), not just some of them on the X most popular websites.

[0]: https://wp.josh.com/2019/05/06/breaking-news-google-adwords-...

Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Wednesday May 29, 2019 @10:10PM (#20047743)
It has the advantage of being faster, with the disadvantage of being less dynamic. Existing rule lists will need to be slimmed down. That's not necessarily a bad thing, because all they ever do is grow without being pruned of old rules.

It seems to me people are upset because they read the title and misinterpreted it to me that adblocking as a whole is going away. But to be fair, even the article itself does a poor job of clarifying that.

Re:Google to restrict modern ad blocking Chrome extensions t... by plorkyeran on Wednesday May 29, 2019 @10:30PM (#20047841)
Google has not shared any actual evidence that there's a performance gain to be had. Non-google benchmarks of uBO show it not being a performance problem in the first place, so there simply isn't much room to be faster than it.
Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Thursday May 30, 2019 @08:50AM (#20050594)
uBO is not the only adblocker around. It's likely not even the most popular. These changes will apply to all of them, bringing the baseline of performance up.
Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Thursday May 30, 2019 @08:49AM (#20050587)
I wish I could edit this comment to correct a mistake, but HN does not allow it.

>misinterpreted it to mean

Re:Google to restrict modern ad blocking Chrome extensions t... by unreal37 on Wednesday May 29, 2019 @10:19PM (#20047781)
The article says that current ad blocking extensions stops the request from even being made to the ad server, while the new version of Chrome will remove the ability for a plug in to stop a web request.

Seems like a pretty major change to me.

Re:Google to restrict modern ad blocking Chrome extensions t... by cortesoft on Wednesday May 29, 2019 @11:05PM (#20048009)
No, I don't think that is correct. You can still stop a web request, but you can only stop it by providing chrome with a list of url patterns to block. The current method passes the url being requested to the extension, which can then decide to block it or not.

The new way has the extension give a list of patterns to block to chrome, and from there it will block any request that matches.

The stated reason is that this is for privacy, to prevent extensions from being able to gather data about every request a browser makes. Currently, a malicious extension could send every url a user visits to some central collection server. The new way prevents that.

Is the trade off worth it? I personally think no, but I do think many people don't realize that as blockers have the capability to collect every url you visit if they wanted.

Re:Google to restrict modern ad blocking Chrome extensions t... by shawnz on Thursday May 30, 2019 @04:50AM (#20049460)
It's not for privacy, the people who were saying that are either mistaken or intentionally lying. It's clear to see because the observational capabilities of the API aren't being removed -- only the blocking capabilities. So the privacy issue is still there. Supposedly, this change is just for performance.
Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Thursday May 30, 2019 @08:46AM (#20050560)
>It's not for privacy, the people who were saying that are either mistaken or intentionally lying.

They're not lying. This was listed as one of the reasons by Google.

>The declarativeNetRequest API provides better privacy to users because extensions can't actually read the network requests made on the user's behalf.

https://developer.chrome.com/extensions/declarativeNetReques...

Re:Google to restrict modern ad blocking Chrome extensions t... by shawnz on Thursday May 30, 2019 @09:27AM (#20050889)
What I mean is the fact that they are deprecating the blocking API. That wasn't an action taken for privacy's sake. Otherwise, why wouldn't they deprecate the observational API too?
Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Thursday May 30, 2019 @10:14AM (#20051317)
I don't know. It's a very fair question.
Re:Google to restrict modern ad blocking Chrome extensions t... by cortesoft on Thursday May 30, 2019 @06:06AM (#20049744)
Oh really? Damn
Re:Google to restrict modern ad blocking Chrome extensions t... by Rebelgecko on Thursday May 30, 2019 @01:26AM (#20048643)
Does it actually prevent that though? Is there no other mechanism that lets extensions know the URL of the current page?
Re:Google to restrict modern ad blocking Chrome extensions t... by SquareWheel on Wednesday May 29, 2019 @10:39PM (#20047878)
It is a major change. Manifest V3 works more like Safari's content blocking.