280
submitted 1 month ago by astro_ray@lemdro.id to c/firefox@lemmy.ml

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.

you are viewing a single comment's thread
view the rest of the comments
[-] LWD@lemm.ee 2 points 1 month ago* (last edited 1 month ago)

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

This is also true for Google's Chrome

[-] unwarlikeExtortion@lemmy.ml 2 points 1 month ago* (last edited 1 month ago)

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).

this post was submitted on 04 Aug 2024
280 points (95.2% liked)

Firefox

17302 readers
900 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS