Technology

59174 readers

3285 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

507

4 browsers that will continue to support uBlock Origin and other ad blockers with Manifest V2 (www.xda-developers.com)

submitted 2 months ago by [email protected] to c/[email protected]

104 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 2 months ago (1 children)

uBlock origin won’t work on Vivaldi

Will the Vivaldi Ad Blocker be affected by the Manifest V3 changes? I made some architectural choices early on that I believe should keep it functional, regardless of the Manifest V3 changes.

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (1 children)

Could we keep using our ad-blocking extensions in Vivaldi?

But, “Wait”, I hear you say, “Doesn’t that mean that basically, Vivaldi might be able to keep webRequest intact just by bypassing the checks for enterprise environments? Could we keep using our adblocking extensions in Vivaldi?”

This certainly sounds plausible, but it is not something that we can promise without seeing what ends up happening in the code itself. If there is an easy way to keep webRequest functioning as it did for a while longer, we’ll consider doing it.

However, it is important to note that extension ad blockers often depend on other APIs that are removed in Manifest V3 (and probably much harder to bring back), so there is no guarantee that simply keeping the blocking version of webRequest alive is going to be enough, without some work from extension maintainers.