this post was submitted on 09 Jun 2026
1162 points (99.5% liked)

Technology

85297 readers
3896 users here now

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

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
1162
Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow (www.neowin.net)
submitted 1 day ago by spaghettiwestern@sh.itjust.works to c/technology@lemmy.world
484 comments fedilink hide all child comments
 

For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.

What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151.

you are viewing a single comment's thread
view the rest of the comments
[–] rklm@lemmy.dbzer0.com 3 points 1 day ago* (last edited 1 day ago) (2 children)

I did my testing before the AI features were implemented, and I tested a variety of custom profile settings for firefox (and floorp and librefox) and custom chrome flags for ungoogled chromium (and brave)...

Granted, I was using benchmarks, but the differences are somewhere around 15-30% on my machine on Arch

Edit: These are the benchmarks I ran

[–] spaghettiwestern@sh.itjust.works 4 points 1 day ago (1 children)

Interesting running those... Haven't had to worry about benchmarks on my system, both Chrome and FF are plenty fast. I do wonder how the performance of Chrome with ads would compare to Firefox with the same ads blocked? Every once in a while I use some one else's computer and can't believe how many animated ads show up on pages I frequent.

Do you just put up with the ads or block them another way?

[–] rklm@lemmy.dbzer0.com 1 points 1 day ago

MV2 has always worked on ungoogled chromium, so I just use uBo. I agree with most folks that ads are not an option XD

[–] fartsparkles@lemmy.world 4 points 1 day ago (1 children)

Have you tried tweaking user.js?

[–] rklm@lemmy.dbzer0.com 1 points 1 day ago

Yes I've used a variety and rolled my own. Tbh the differences are difficult to measure