cross-posted from: https://lemmy.zip/post/20260243
Google Chrome warns uBlock Origin may soon be disabled
Google Chrome is now encouraging uBlock Origin users who have updated to the latest version to switch to other ad blockers before Manifest v2 extensions are disabled.
For Firefox forks, it’s viable since the forks aren’t doing all that much in the grand scheme of things. That isn’t to say what they’re doing is in any way bad, it’s just that there’s no need to reinvent the wheel.
Firefox is a secure browser and already has 99% of the work done. Most changes which forks make can be done just by changing the config. Some unfortunately have to be made seperately, and that does require extensive testing. Some can even be lifted from other open-source projects.
Separating from source just isn’t viable. Something nuclear would need to happen for any fork to decide to seperate from Firefox. If we just look at the Chromium side of things, Microsoft found it easier to switch to Chromium than to keep making IE/Edge from scratch, and Microsoft surely has a lot of resources to burn.
This is also true for Google’s Chrome
As far as I know Google doesn’t let some pretty basic stuff from Crome into Chromium, for example translation (might even go as far as the inbuilt password manager). Potential forks either lose those features or have to implement them seperately.
Now that Manifest v3 is rolling out, apparently Google is able to somehow block the change from being easily reverted which is additional developmental load (or just show ads). Manifest v3 won’t impact Brave too much since it only applies to extensions, while their adblocking is baked-in, but it’s worse than uBO.
Firefox is fully open-source and doesn’t artificially make enabling adblock an issue which might attract more simpler forks (as opposed to Opera, Brave and Edge having companies backing them, Firefox forks mostly have volunteer developers or open source collectives making them).