Will Opera be nixing certain adblockers like Google Chrome will be doing?

[A Former User]

A Former User @leocg last edited by

@leocg Depends on if they like ads or not I suppose. On more than a few forums I've spoken to quite a few Chrome users who will jump ship when the API change comes into effect.

It's the main reason I downloaded Opera from the Ubuntu repo. I already have Firefox but I want a good back-up browser.

[A Former User]

A Former User last edited by

I really hate it when browser devs use the "we have our own adblock, built in and this will stay" as an advantage.
Who considers opera's built in adblock to be a good one? Because I don't.

Proof

Both those screenshots are from facebook's ads and were taken the first days I started using chromium opera, back in early 2017, with no extra extensions yet.
The first one shows the original ad frame and no adblock at all, and the second one shows the same frame with opera's built in adblock. As it seems, all opera's adblock did was to filter the "Sponsored" word on the top and nothing more.
And that was the moment I disabled it and installed ublock origin to opera too.

[A Former User]

A Former User last edited by

uBO is the best adblocker. I was just wondering if push came to shove that I could surf with only Opera's inbuilt blocker.

I use a combination of ABP and Ghostery Lite on Safari.

I use uBO on Firefox.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@skyrim2011 I still think that everything will depend on how difficult and how costly will be to avoid the changes in Chromium.

[A Former User]

A Former User last edited by

Pretty sure Opera will see this as their chance to push their inbuilt ad blocker and won't put much energy into restoring the old api.

[blackbird71]

blackbird71 last edited by

At this point in time, it's way too early to know how this will unfold for various browsers, Opera included. At least in part, that's because the final version of the new chromium API and any 'permanent' changes/deprecation of the old API have not been decided upon. Only then, and based upon that impact to browser coding, will it be possible to determine how the various browsers will be impacted. Those impacts will determine the economics or possibility of various browsers preserving existing ad-blocking capabilities or extension compatibility. Right now, it appears that everyone's at the mercy of how the chromium changes are actually implemented, and that's where the battle is being fought between app and chromium developers.

[A Former User]

A Former User @leocg last edited by

@leocg said in Will Opera be nixing certain adblockers like Google Chrome will be doing?:

@skyrim2011 I still think that everything will depend on how difficult and how costly will be to avoid the changes in Chromium.

Well, considering that the enterprise version of Chrome isn't affected by this, how exactly are you making this corollary?

I'm no software engineer but I wouldn't have thought it would be prohibitively expensive in keeping the webRequest API and not replacing it with the declarativeNetRequest API.

I guess that's what's happening with the enterprise version of Chrome.

But as I stated, I'm no software engineer.

[A Former User]

A Former User @blackbird71 last edited by

@blackbird71

Excellently stated.

[A Former User]

A Former User @Guest last edited by

@thisisausername

Well, if it works well, I don't mind.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@daveski17 There is already a public version of Chrome/Chromium with the change?

[A Former User]

A Former User @leocg last edited by

@leocg said in Will Opera be nixing certain adblockers like Google Chrome will be doing?:

@daveski17 There is already a public version of Chrome/Chromium with the change?

All I know is that Google have backtracked and now claim the API change won't affect the adblocking functionality in enterprise versions.

https://9to5google.com/2019/05/29/chrome-ad-blocking-enterprise-manifest-v3/

[A Former User]

A Former User last edited by

@daveski17

This is what happens if there is only one API from a company with market dominance.

[A Former User]

A Former User @Guest last edited by

@skyrim2011 Bring back Presto I say lol.

[A Former User]

A Former User last edited by

Good news everyone!

Additionally, we are currently planning to change the rule limit from maximum of 30k rules per extension to a global maximum of 150k rules.

https://blog.chromium.org/2019/06/web-request-and-declarative-net-request.html

[A Former User]

A Former User last edited by

Dude, you're not falling for that, right?

[A Former User]

A Former User @Guest last edited by A Former User

@jimunderscorep

Ad blocker developers and filter list authors had demanded 300,000 elements per extension. For users combining multiple lists, 150,000 elements might not be enough.

To me, this blog post looks like an attempt at appeasement and justification.

[A Former User]

A Former User @Guest last edited by

@yanta said in Will Opera be nixing certain adblockers like Google Chrome will be doing?:

@jimunderscorep

Ad blocker developers and filter list authors had demanded 300,000 elements per extension. For users combining multiple lists, 150,000 elements might not be enough.

To me, this blog post looks like an attempt at appeasement and justification.

Yes, that's exactly what I thought.

[A Former User]

A Former User last edited by

More Googleballs

https://gizmodo.com/google-no-of-course-were-not-slowly-killing-ad-block-1835495590

“There’s been a lot of confusion and misconception around both the motivations and implications of this change, including speculation that these changes were designed to prevent or weaken ad blockers,” Google writes in a separate blog detailing the differences between the two APIs. “This is absolutely not the goal. In fact, this change is meant to give developers a way to create safer and more performant ad blockers.” op cit

At least on the surface, this looks like a good thing. But there are a few niggling details that call that into question. Back in January, the Register reported that Adblock Plus and similar plugins relying on basic filtering would still be able to function, while more sophisticated ones like uBlock Origin and uMatrix would be completely borked. The site also noted that well, Google had conveniently paid Adblock Plus to let their own ads pass unblocked in the software. In a statement, Ghostery, another popular adblocker, pointed out the Declarative Net Request API was limited, and that it wouldn’t be possible to “modify or kill potentially dangerous or privacy-invading requests.” op cit

[A Former User]

A Former User last edited by

@daveski17 + @yanta
Well... ubo is malfunctioning on my firefox for several days each month, allowing may ads to pass through. But it never had an issue on my chromium and opera.
If the manifest v3 change will force me to change to a different browser, that will be firefox... or use dns blocking.
But I do not want to. So, that post from google gives me some hope, which may be false hope, but it is still some hope.

[A Former User]

A Former User @Guest last edited by

@jimunderscorep
I've never had any issues with uBO and Firefox. I don't have many extensions on Firefox. Maybe you are having some conflict with another extension?