I, for the first time ever, uninstalled chrome/chromium from my computers. It pains me because I liked it overall, and firefox isn't happy with my 2009 laptops. Maybe chrome devs mistake will be the air gap that creates a new leader from another group.
FF and Safari were the only browser that worked well on my 2009 MBP ... until FF went multi process, and then started using too much ram. Today I think its total ram usage is worse than Chrome.
Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
141–150 of 256 posts
Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#142Earlier quoted context omitted.
My gut feeling is that Google won't pull this stunt with chrome, this is some kind of scare mongering or a PR tactic, I dunno. It doesn't make a logical sense because if they are banning the ad-blockers, it means they accept that chrome is largely used by power users who can install these blockers (otherwise, what's the need?). But they should realize that a power user who installs an addon can just as easily move to…
>It doesn't make a logical sense because if they are banning the ad-blockers... To be clear, you can still block ads under Manifest v3. I don't know where this idea that you suddenly won't be able to block ads came from, but somebody is being dishonest about it.
Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#143Tried Opera on Mac OS - half of toggles on the Settings page is not rendered - "Pref not found for element SETTINGS-TOGGLE-BUTTON in SETTINGS-APPEARANCE-PAG". It was so epic trash - removed instantly. They obviously don't test it on Mac OS. Tried Vivaldi - render sites with errors (some images missing). 0 plugins installed. Not acceptable, removed. Brave - I really hate person who run this project and how he is tryin…
Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#144Earlier quoted context omitted.
The problem you described actually happened with Firefox and Firefox forks not too long ago. Mozilla kicked out all traditional Firefox add-ons from their repository to "replace" them (note: they didn't actually replace the vast majority) with chrome style webextensions. Firefox forks were forced to implement and run their own add-on hosting system and API, and navigate the complex legal waters of re-hosting the add-…
Ironically Firefox killed their extension API to be compatible with Chrome's extensions. Now they probably don't want to be compatible with the new Chrome API.
Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#145Earlier quoted context omitted.
>It doesn't make a logical sense because if they are banning the ad-blockers... To be clear, you can still block ads under Manifest v3. I don't know where this idea that you suddenly won't be able to block ads came from, but somebody is being dishonest about it.
Ad blocking capabilities are limited and there's no API to implement advanced rules like media size limiting. For example manifest v3 has no way to implement the full EasyList.
Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#146Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#147I, for the first time ever, uninstalled chrome/chromium from my computers. It pains me because I liked it overall, and firefox isn't happy with my 2009 laptops. Maybe chrome devs mistake will be the air gap that creates a new leader from another group.
I got a new computer recently (old one died), and because of this change I will not install Chrome on the new computer. I’m planning to use Edge for anything Google-specific like Google Docs or Sheets, and Firefox for everything else. Unfortunately, my wife has a Chromebook and it’s hard to convince her that her very cheap, almost-disposable laptop should be replaced with something more expensive just to avoid Chrome…
Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#148Earlier quoted context omitted.
Ironically Firefox killed their extension API to be compatible with Chrome's extensions. Now they probably don't want to be compatible with the new Chrome API.
> Ironically Firefox killed their extension API to be compatible with Chrome's extensions. This is misleading. They deprecated the old API primarily to be able to do multi-process and get rid of XUL.
Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#149Re: Opera, Brave, Vivaldi to ignore Chrome's anti-ad-blocker changes
#150The problem at this point isn't whether chrome will disable it... It can be added back, probably fairly easily as google intents to keep it around for "enterprise" anyway, so it's probably just gonna end up changing/removing one if-statement. If not, then the code already exists and has to be merged back in. The problem is distribution of the actual extensions, as Vivaldi kinda pointed out, as the other browsers most…