Live data from Hacker News

Google to restrict modern ad blocking Chrome extensions to enterprise users

9to5google.com

31–40 of 909 posts

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#31
post #11
post #5

Here are browsers that aren't just 'not Chrome,' they are better. Brave: https://brave.com/ Firefox: https://www.mozilla.org/en-US/firefox/

Personally I use and can recommend ungoogled-chromium https://github.com/Eloston/ungoogled-chromium

> ungoogled-chromium retains the default Chromium experience as closely as possible

It sounds like they would also be removing ad-blocking then

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#32

Google is essentially saying that Chrome will still have the capability to block unwanted content, but this will be restricted to only paid, enterprise users of Chrome. Never heard of a paid version of Chrome before! Can anyone elaborate on this? I gotta say I'm kind of glad Google is doing this. It will force me to finally abandon Chrome, something I should have done awhile ago.

This is essentially not true.

Content can still be blocked with extensions, but it will be more difficult to handle large block lists.

See this comment from the author of uBlock Origin and uMatrix.

https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss...

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#33

Earlier quoted context omitted.

The original creators of Opera have been building out Vivaldi for a while, which has the specific design goal of being a browser for power users https://vivaldi.com/

Without source available, it seems like it's targeted for a section of power users.

I have no idea if it would compile and is actually complete, but Vivaldi does do sourcecode tarballs.

https://vivaldi.com/source/

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#34

Google is essentially saying that Chrome will still have the capability to block unwanted content, but this will be restricted to only paid, enterprise users of Chrome. Never heard of a paid version of Chrome before! Can anyone elaborate on this? I gotta say I'm kind of glad Google is doing this. It will force me to finally abandon Chrome, something I should have done awhile ago.

> Never heard of a paid version of Chrome before!

Is there such a thing? The "paid" part comes from the article's gloss, not from Google. I could see it instead being "this is a switch you can turn on in Group Policy."

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#35
post #10

I'm glad I already made the switch to FireFox. I only use Chrome to access Google apps, because for some strange reason they work a lot better in Chrome... The only thing I miss is a Session Buddy equivalent. When my computer crashes, it's nice to be able to restore all my tabs and windows, and also it's nice to be able to close a bunch of windows when I travel and then go back to my tab state from three weeks ago.

I use a Firefox addon called Session Boss. It might be what you're looking for.

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#36
post #22

> Firefox is available on all platforms (including Chrome OS via the Android or Linux app) Maybe this is a viable solution on brand new chromebooks, but on my Acer R11 both Android apps and Linux containers run pretty poorly. I use an Android app as my password tool just fine, but trying Firefox was a rather poor experience. And the linux container just dogs trying to do anything. I have Ubuntu loaded on via crouton…

I run Firefox on my Chromebook in Ubuntu via Crostini, works pretty well and appears right next to native ChromeOS apps on the screen.

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#37
post #25
post #16

Earlier quoted context omitted.

Maybe it's unfair, but I can't help but think of Brave as just a scheme to push their cryptocurrency. They're removing the website's ability to monetize and replacing it with their own system. That seems gross.

You're not wrong about what it boils down to, but, I'm all for it. I didn't mind ads, generally, until I did. Until they started hijacking your browser, redirecting you, doing popups. Ad people have shown they cannot be trusted on the whole. What Brave seems to be doing is doing their own 'safe ads' system, and sharing the money. It will likely be less for the content creators, but as a 'at-my-wits-end-with-ads' Brav…

If you look at the benchmark results, aggressively stripping ads and tracking can result in pages loading twice as fast and hours of extra battery life. I'm happy to pay money to view your website, but modern web ads are a ridiculous and punitive payment scheme.

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#38

Google is essentially saying that Chrome will still have the capability to block unwanted content, but this will be restricted to only paid, enterprise users of Chrome. Never heard of a paid version of Chrome before! Can anyone elaborate on this? I gotta say I'm kind of glad Google is doing this. It will force me to finally abandon Chrome, something I should have done awhile ago.

Check out Ungoogled Chromium, it's pretty great.

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#39
From the author of uBlock on this:

What we see are the public statements, for public consumption, they are designed to "sell" the changes to the wider public. What we do not see is what is being said in private meetings by officers who get to decide how to optimize the business. So we have to judge not by what is said for public consumption purpose, but by what in effect is being done, or what they plan to do.

This is how personally I see the deprecation of the blocking ability of the webRequest API in manifest v3:

In order for Google Chrome to reach its current user base, it had to support content blockers -- these are the top most popular extensions for any browser. Google strategy has been to find the optimal point between the two goals of growing the user base of Google Chrome and preventing content blockers from harming its business.

The blocking ability of the webRequest API caused Google to yield control of content blocking to content blockers. Now that Google Chrome is the dominant browser, it is in a better position to shift the optimal point between the two goals which benefits Google's primary business.

The deprecation of the blocking ability of the webRequest API is to gain back this control, and to further now instrument and report how web pages are filtered since now the exact filters which are applied to web page is information which will be collectable by Google Chrome.

https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss...

Re: Google to restrict modern ad blocking Chrome extensions to enterprise users

#40
post #7

Modern firefox is an awesome experience. The only reason I use Chrome is because the dev tools are that good.

Do you have some reasons you prefer chrome dev tools to FF? I consider FF to have the more featureful devtools, for example the sheer amount of stuff under the styles tab, you can tweak fonts in browser. I do remember back when I used chrome there would be new `console.x` features that were chrome only from time to time, but after I switched to FF I never really looked back

Chrome's DevTools handles developing large unbundled webapps better. When your loader is reaching to the fs for thousands of source files for a single page load, Chrome performs significantly better than Firefox. Same goes for Ctrl+P jumping to files and debugging performance.

It's gotten a lot better over the last two years, especially when FF DevTools got support for source maps and TypeScript debugging, but it still lags enough to keep me using Chrome for my job, Firefox at home.

Post reply on HN