Re:Chrome pushes forward with plans to limit ad blockers in ...
by jacooper on Thursday November 23, 2023 @02:40PM
(#38396638)
Brave isn't affected by this anyway, brave shields don't depend on the extension API.
Also Gecko is just a factually worse engine, that's why they didn't use it.
Re:Chrome pushes forward with plans to limit ad blockers in ...
by bonzini on Thursday November 23, 2023 @02:56PM
(#38396821)
Gecko is not worse, though it used to be worse before Electrolysis landed. It's just that Mozilla Corp is mostly kept alive by Google so might as well remove the indirection and go straight to the browser that Google maintains
Re:Chrome pushes forward with plans to limit ad blockers in ...
by idonotknowwhy on Thursday November 23, 2023 @06:07PM
(#38398750)
How much money do you reckon it costs for just the Firefox browser?
I know Mozilla waste a lot of effort on projects like Firefox OS, the Firefox mobile, politics, etc. But the actual browser it's self and it's hosting?
I just wonder if they end up dropping Manifest V2, if a patron model would work to maintain a fork properly...
Re:Chrome pushes forward with plans to limit ad blockers in ...
by bonzini on Friday November 24, 2023 @04:51AM
(#38402202)
Those projects exist because they are within the scope of Mozilla Foundation, which is wider than just building a browser.
Re:Chrome pushes forward with plans to limit ad blockers in ...
by jacooper on Friday November 24, 2023 @02:51PM
(#38407511)
It's faster, supports more features and is more secure, especially on Linux [1].
1. https://madaidans-insecurities.github.io/firefox-chromium.ht...
Alternatively it could be that all alt browser companies will maintain one chromium fork that preserves manifest v2. Or V3 but with a lot more rules.