Google Chrome change that weakens ad blockers begins June 3rd

[vtqhtr413]

Content source

https://www.bleepingcomputer.com/news/google/google-chrome-change-that-weakens-ad-blockers-begins-june-3rd/

Google is continuing with its plan to phase out Manifest V2 extensions in Chrome starting in early June 2024, weakening the abilities of ad blockers.

Google says this decision was made based on the community's progress and feedback, which were deemed satisfactory to continue without further delays.

Starting June 3, 2024, with Chrome version 127, users with active Manifest V2 extensions will see warnings on Chrome Beta, Dev, and Canary channels, while extensions still using Manifest V2 will lose their "Featured" badge.

Gradual disabling of V2 extensions will follow on the stable Chrome release, with recommendations for V3 alternatives. Users can temporarily re-enable their Manifest V2 extensions, but this option will eventually be removed.

Enterprises using the "ExtensionManifestV2Availability" policy will be exempt until June 2025, so they will be given an extra year to transition to Manifest V3 compatible add-ons.

Google Chrome change that weakens ad blockers begins June 3rd

Google is continuing with its plan to phase out Manifest V2 extensions in Chrome starting in early June 2024, weakening the abilities of ad blockers.

www.bleepingcomputer.com

 

[nicolaasjan]

Enterprises using the "ExtensionManifestV2Availability" policy will be exempt until June 2025, so they will be given an extra year to transition to Manifest V3 compatible add-ons.

It should be noted that 'normal' users can apply this policy as well.

To do so, open the command prompt as administrator and enter the following:
reg add "HKLM\SOFTWARE\Policies\Google\Chrome" /v "ExtensionManifestV2Availability" /t REG_DWORD /d "2" /f

Relaunch Chrome.
(after that Chrome will tell you: "Your browser is managed by your organization")

 

[nicolaasjan]

Here you will find a way to keep Manifest v2 extensions working on Chrome/Chromium 138,139 and 140:

https://old.reddit.com/r/uBlockOrigin/comments/1itw1bz/end_of_support_for_ubo_on_chrome_chromium/

This is uBO working on Chromium dev build 140.0.7290.0 :

I had to add the following parameters to the Chromium launcher (Linux):

chrome --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

 

[TairikuOkami]

Merely blocking tracking blocks 99% ADs, we just need a smart v3 extension that properly implements cosmetic filtering with DNS filtering.

 

[aidunno]

Merely blocking tracking blocks 99% ADs, we just need a smart v3 extension that properly implements cosmetic filtering with DNS filtering.

what do you use for blocking tracking?

 

[aidunno]

Here you will find a way to keep Manifest v2 extensions working on Chrome/Chromium 138,139 and 140:

https://old.reddit.com/r/uBlockOrigin/comments/1itw1bz/end_of_support_for_ubo_on_chrome_chromium/

This is uBO working on Chromium dev build 140.0.7290.0 :

View attachment 289479

I had to add the following parameters to the Chromium launcher (Linux):

chrome --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

so many extensions

 

[Sorrento]

Or you could use Brave & Firefox?

 

[TairikuOkami]

what do you use for blocking tracking?

NextDNS only.

 

[nicolaasjan]

Shortcut parameters still working on Chromium dev build 141.0.7377.0
Maybe on 142 they'll stop working.

 

[Zero Knowledge]

Temp move. Eventually you won't be able to downgrade to MV2. Sad that they use 'security' as an excuse for this crud move.