Google making Chromium block adblockers?

samuvuo

@Priest72 said in Google making Chromium block adblockers?:

The new API just limits the filterlist numbers.

The problem with the new API (not finalized yet, though, if I'm not mistaken) is not the entry limit number, but crippled down algorithm.

The developer of Ublock Origin, Raymond Hill, said (emphasis mine) [1]:

"Key portions of uBlock Origin and all of uMatrix use a different matching algorithm than that of the declarativeNetRequest API. Block/allow rules are enforced according to their specificity, whereas block/allow rules can override each others with no limit. This cannot be translated into a declarativeNetRequest API (assuming a 30,000 entries limit would not be a crippling limitation in itself).

There are other features (which I understand are appreciated by many users) which can't be implemented with the declarativeNetRequest API, for examples, the blocking of media element which are larger than a set size, the disabling of JavaScript execution through the injection of CSP directives, the removal of outgoing Cookie headers, etc. -- and all of these can be set to override a less specific setting, i.e. one could choose to globally block large media elements, but allow them on a few specific sites, and so on still be able to override these rules with ever more specific rules.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2#c23

samuvuo

@JohnConnorBear said in Google making Chromium block adblockers?:

Limiting the entries in the list is not a big deal because blocking by keywords is outdated.

Exactly.

Clever PR play from Google though, increasing the rule limit from 30 000 to 150 000 after the initial commotion. Masses (the "average users") understand numbers. "Google listens to their users, limits have been raised, all is well, no need to worry"

Steffie

@samuvuo This continues to be my abiding concern as well. IMO anyone focusing merely on the numbers has let themselves be gamed by gargle, coz that is simply missing the point. If the day comes that i can no longer use uMatrix in V & my other chromium browsers, then that'll be the day i uninstall them all & use only Firefox-Nightly... which of course itself is approaching a different kind of existential crisis. Sigh.

Carighan

@Priest72 said in Google making Chromium block adblockers?:

There are approximately 5-6million users of ublock origin and if google makes the wrong decision then they will choose other non chromium browsers.Because google couldn't care less about it's users i expect firefox will gain a lot of extra users in the coming years.

That's fast becoming a big problem though: There is only one non-Chromium browser left, really.

And for all the snazzy features like Containers and dFPI Firefox has, its development also seems to be in shambles with odd changes, deteriorating UI modifications, removal of features and management overpaying themselves to extract extra money before the ship sinks.

It's... a mess. More so because that's all there is left now that Microsoft has swapped to Chromium.

code3

Does Vivaldi have a plan for this yet? I wonder if they could cooperate with other chromium browsers...
At least if Vivaldi has better support for javascript/font blocking and makes an alt web store these changes would not be so bad.

derDay

@code3 said :

Does Vivaldi have a plan for this yet?

huh? there's already an internal ad blocker which can import/connect to external resources.
You are right, that the internal blocker is limited compared to uBlock (or similar extensions), but that's already more than no blocker

Catweazle

~~Roko's Basilisk~~ Gargle hate adblockers

code3

@derDay Yeah, I know, I don’t even use uBO but I don’t like that Google has so much power over Vivaldi. I also use other extensions that will likely be affected. Adblockers won’t be banned, they will just be less powerful, so Vivaldi’s as blocker isn’t a replacement. I also don’t get how all this helps google, they would still be blocked by adblockers. I know it could help Google a bit, and pave the way for them controlling more.

Anyways, I guess what you’re saying is Vivaldi will not try to leave the old API? Will they have more options for header removal?

derDay

@code3
I'm not a professional in this matter, but as far as I know, is the internal blocker not affected from the eventually removal of the actual API because it doesn't use the API.
perhaps another vivaldian knows more about it in detail.

which features will be added to the internal blocker can nobody say

code3

@derDay Yes, of course. Thank you for your help.
I still have a few questions about what will be affected, but they aren't necessarily for you, just for anyone who knows.

Will I still be able to block referral headers and google headers? Randomize cookies based on name?
Will I still be able to use extensions that inject code into pages?
What about the speed dial generator from @An_dz ?
Has Vivaldi really given up on trying to keep the old api or is it still a possibility?

luetage

@derDay I think Vivaldi uses chrome apis internally, but we can be pretty sure the adblocker will continue to work. Keeping the netrequest api doesn’t make much sense, because as soon as Chrome drops the api, extensions using it will disappear from the store and development will stop. Vivaldi would need to run their own extensions store and then extensions developers would need to cater to this fringe market with specialized extensions. Highly unlikely.

Streptococcus

@Catweazle said in Google making Chromium block adblockers?:

~~Roko's Basilisk~~ Gargle hate adblockers

Of course Google hates adblockers because they themselves are serving ads.