#uBlockOrigin is forever disabled in #Chrome. Why it happened and what to use instead
https://adguard.com/en/blog/ublock-origin-disabled-chrome.html
#uBlockOrigin is forever disabled in #Chrome. Why it happened and what to use instead
https://adguard.com/en/blog/ublock-origin-disabled-chrome.html
I was under the impression that @Vivaldi is going to support Manifest V2 plugins after Chrome drops support, but this message is alarming. What's going on?
control the market. It also means its not going anywhere anytime soon.
3. Manifest V2 is dead. Yes, it is supported by Firefox but it'll be dropped eventually. Maintaining V2 and V3 simultaneously will be exhausting for the Firefox team that's already severly undermanned.
There's no guarantee @brave will support Manifest V2 after Google drops it in Chromium (which it already did I think?).
If you really want Manifest V2, use @firefox (or a fork) where its being maintained officially.
Windows Insider mucked through the options to replace uBlock Origin for those on Chrome.
#uBlockOrigin dead for many as #Google purges #ManifestV2 extensions
#Chrome #adblocker stopped working? Time to look elsewhere
#uBlock recommends a move to #Firefox and use of the extension uBlock Origin, a switch to a browser that will support Manifest v2, or downloading a different extension – #uBlockOriginLite, for example.
https://www.theregister.com/2025/02/24/google_v2_eol_v3_rollout/
Do you still trust an #ad company to block ads or not datamine you?
有用户在 Hacker News 称新版 Google Chrome 已经停用 Manifest V2。
如果希望暂时还原 Manifest V2,可以通过添加企业政策或修改注册表的方式实现。
blog.gslin.org/~
#ManifestV2 #Chrome
Telegram 原文
@jon @Vivaldi Hi! Opera will keep to support #ManifestV2. What does Vivaldi have the plan about this problem? Will Vivaldi support Manifest V2, too? Or other plan?
Opera will always help you block ads natively - Blog | Opera News Manifest
https://blogs.opera.com/news/2024/10/opera-support-manifest-v2-ad-blocking/
> an official Registry hack exists that allows extending the support for MV2 add-ons with the help of the "ExtensionManifestV2Availability" policy that is designed for enterprises. Enabling the policy allows an extended year of support for MV2 add-ons till June 2025.
Und hier nochmal eine Erinnerung, warum wir von #Google unabhängige Browser brauchen: #uBlockOrigin, was die Browsernutzung erträglich macht, fliegt nun wegen der lang angekündigten Umstellung auf #ManifestV3 endgültig aus #Chrome / #Chromium raus. #uBlockLite ist leider komplett kastriert und kann nur rudimentär Werbung blockieren.
#Firefox unterstützt weiter #ManifestV2 und ist die Empfehlung des uBlock Origin Entwicklers gorhill. #Librewolf hat das Add-on vorinstalliert.
#uBlockOrigin ou #ublocklite ? Va falloir choisir, prochainement, en tout cas si vous utilisez #googlechrome (#manifestv3 vs. #ManifestV2).
#firefox n'est pas concerné !
Google начинает избавляться от расширений на Manifest V2 в Chrome
https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html
Manifest V3 (MV3) должен улучшить безопасность и производительность расширений. Это достигается введением ограничений на фильтрацию трафика и внешние обновления. Из-за этого блокировщики рекламы и трекеров, такие как uBlock Origin [1], лишатся своей былой эффективности [2]. Пользователи станут более уязвимы для сбора данных и рекламы: не все трекеры будут блокироваться, а списки фильтров не смогут обновляться часто.
В каталоге Chrome расширения на MV2 уже утратили статус "Рекомендованное", и в ближайшие месяцы браузер будет предлагать заменить "устаревшие" расширения. Вместо uBlock Origin следует использовать Lite-версию [3].
Google будет и дальше ослаблять блокировку рекламы и трекеров. Изменения могут затронуть и другие браузеры Chromium (Edge, Opera, Яндекс). В Brave [4] и Ungoogled Chromium [5] планируется оставить MV2. Firefox работает на своём движке Gecko, Mozilla не планирует убирать поддержку MV2 в нём [6].
[1] https://kooltechtricks.neocities.org/wiki/ublock_origin
[2] https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-asked-questions-(FAQ)#filtering-capabilities-which-cant-be-ported-to-mv3
[3] https://chromewebstore.google.com/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh
[4] https://x.com/brave/status/1771036190445359127
[5] https://github.com/ungoogled-software/ungoogled-chromium/issues/662#issuecomment-1850192208
[6] https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update
No better time to be supportive to the users of unfortunate #Chromium browsers by directing to something not as contrived. For example, instead of drowning #ManifestV3 altogether we could look at the implementations like Firefox that retain compatibility with #ManifestV2 and don't ruin the effective use of ad blocking features. Way to keep extension development modern, all the while disregarding #Google's terrible mistake.
@PrivacyDigest Now is the perfect time to migrate to #firefox, #vivaldi , #brave, and other browsers that are NOT removing #ManifestV2. Take your browser back and protect your privacy, support your right to control tracking and ad blocking on your systems. Might also be a good time to look into network level blocking with #pihole, #adguardhome, and others.
“#ManifestV2” extensions nuked, V3 cripples ad blockers.
#Google following through on its threat to kill #AdBlockers. Its language is friendly and understanding—gushing with “ongoing dialogue” and “addressing developer feedback”—but the meaning is clear: Today’s full featured, privacy focused #Chrome #extensions are living on borrowed time.
#Firefox and #Safari are the only major browsers unaffected. In today’s #SBBlogwatch, we muster #Mozilla. At @TechstrongGroup’s @SecurityBlvd: https://securityboulevard.com/2023/11/google-manifest-v3-ad-blockers-richixbw/?utm_source=richisoc&utm_medium=social&utm_content=richisoc&utm_campaign=richisoc
Zadziwia mnie jak bardzo różni się podejście #Google i #Mozilla w kwestii wtyczek do przeglądarek. Podczas tworzenia rozszerzenia do #Chrome okazało się, że wiele internetowych poradników i porad jest nieaktualnych, ponieważ Google jakiś czas temu przestało obsługiwać #ManifestV2 (czyli taki plik tłumaczące przeglądarce jakie uprawnienia potrzebuje rozszerzenie, jak się nazywa itd.) w silniku #Chromium i należy tworzyć rozszerzenia już formacie w #ManifestV3.
Zupełnie inaczej sytuacja wygląda w przypadku #MozillaFirefox – jak tylko załadowałem wtyczkę do sklepu, pojawił się komunikat, że moja wtyczka jest oparta o Manifest V3, a zalecane jest korzystanie z Manifest V2, ponieważ starsze wersje #Firefox nie obsługują V3, gdyż jest to stosunkowo nowość