I’ve read some things online about it all but I’m not a total IT boff. Is it really true that Brave browser won’t be able to block ads once the changes are made next year?
Ps. I use Firefox with uBlock but my SO and most of my clients absolutely love Brave
You must log in or register to comment.
Manifest V3 will not prevent Brave from blocking ads. We built ad blocking into the browser itself so it will not be affected by Google changing its rules for extensions.
Man, I hope Vivaldi keeps uBlock somehow or beefs up their built in ad blocker, or I will be forced back to Firefox. Ugg, I miss active proxy based blockers like proxomitron…
deleted by creator
Fennec is even better than Firefox, it’s the same source but recompiled to allow all add-ons in the main app. So basically a stable Firefox nightly, if you wish.
It’s maintained by the folks behind the f-droid app store themselves, so arguably a highly trusted source.
Sync to Firefox desktop fully implemented and working.
I’ve been using Mull, a fork of Fennec
Oh nice, I’ll check that out as well. What would you call the core differences?
Supposedly its got more security/privacy/anti-tracking. From what i can tell there is no major differences besides it using this configuration user.js by default
Ah nice, sounds great. I’ll test it over the weekend when I got some free time.
True concern from a person that just got rid of chrome (finally) and switched to brave, how is it garbage? o_o
deleted by creator
Can you provide reasons for your claim? I’m curious to know what makes Brave garbage
deleted by creator
It is best to move to Firefox because fundamentally the chromium project thrives because of Google ,an Ad company. It is not worth using chromium derivatives.
Out of interest, since Chromium is open source, is there anything stopping Opera, Edge, Brave, etc. just mantaining support for the old manifest? Like, I’m not sure why this is such a big deal for anything other than Chrome and Chromium.
deleted by creator
When you do that you’d have to port every single security patch and new feature manually into your fork. And it gets even worse: Because you deviate from the original implementation you continue to use outdated code that nobody is patching at all.
So you can absolutely do that, but in a year you’ll have your own browser with tons of security issues and no manpower to find and fix them.
Basically you’d be using an old browser version.
