Technology

59569 readers

4136 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

506

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

submitted 3 months ago by fne8w2ah@lemmy.world to c/technology@lemmy.world

92 comments fedilink hide all child comments

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

[–] clay_pidgin@sh.itjust.works 6 points 3 months ago (1 children)

Vivaldi does a lot of adblocking natively, and they are maintaining V2 as long as they can, which based on info from Google is summer 2025 but might change.

[–] SteveFromMySpace@lemmy.blahaj.zone 22 points 3 months ago (2 children)

Yes but that doesn’t change the fact that in 10mo uBlock origin won’t work on Vivaldi. The perils of chromium builds. I don’t blame Vivaldi, I’m just stating a fact. They won’t support Mv2 and uBlock origin will not work.

[+] helenslunch@feddit.nl 2 points 3 months ago* (last edited 4 weeks ago) (1 children)

[deleted]

[–] Ilandar@aussie.zone 2 points 3 months ago* (last edited 3 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.

[–] clay_pidgin@sh.itjust.works 1 points 3 months ago

Not arguing, just adding context from their blog.