Google Is Killing uBlock Origin. No Chromium Browser Is Safe
quippd.comGreat in-depth article, recommended read ! Also, go and install Firefox - uses less RAM than Chrome(ium-based), more privacy-focused, faster and blocks ads fully.
Any suggested customizations or additional extensions? I use FF at the office but mostly Chrome at home, and the transition might be a bit painful.
No Script - Whitelist the Javascript for any and all sites
Bit of a pain to use sometimes, but I've gotten used to fine-tuning exactly what I allow to run.
ublock origin (turn on a lot of the extra filters)
sponsorblock (turn on a lot of the extra filters)
sidebery
Firefox Multi-Account Containers
Uppity
Vimium
I still don't care about cookies
Decentraleyes
Temporary containers
Clean URLs
Stylus
>Other Chromium browser vendors have claimed that they will continue to support MV2 based content blockers, later revealing that they were unwilling to support the code once Google removed it.
But Brenden said: >Brave will support uBO and uMatrix so long as Google doesn’t remove underlying V2 code paths (which seem to be needed for Chrome for enterprise support, so should stay in the Chromium open source). Will Google Chrome Web Store really kick them out over V2? We will host if needed.
So it seems like Chrome Enterprise needs V2 code paths so not all Chromium browsers are botched but Chrome Store can kick them off the Store or maybe they will stay as legacy extensions? Time will tell.
Except that google already told that they will not keep V2 for enterprises..
enterprises have a 6 months extension compared to the rest of people, actually anyone can enable a policy that re-enable V2 but google said that it will maintain that only for additional 6 months..
After that they will remove V2 entirely even from enterprises..
i doubt that google will keep the code around to support V2 for long after that.. Browsers that want to keep it will have to maintain the code themselves and deal with any problems and costs that it causes..
>i doubt that google will keep the code around to support V2 for long after that.. Browsers that want to keep it will have to maintain the code themselves and deal with any problems and costs that it causes..
That's bad but yea Chromium browsers can fork off and keep legacy V2 code.
well.. that is exactly what i said..
But maintaining a fork with the legacy v2 code is not trivial to do or cheap..
Google has the money to maintain a browser and i do not even trust then.. i for sure would never trust any of those forks..
Firefox needs some good news.