- cross-posted to:
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
You must log in or register to comment.
The only silver lining was they were also going to disable their party cookies, but they nixed that idea and kept this one. I’m done rooting for chrome.
Reminder #891,814 to stop using Chrome and Chromium browsers and to stop supporting Google’s web monopoly.
3 more will do it! :p
Why Chromium based browsers? I understand using Chrome might help Google, but how does using other browsers based on Chromium help them? By increasing market share?
Yes. It gives them leverage when working on standard specs. And it can lead to stagnation. The latter didn’t happen yet, but they already tried to push their agenda multiple times already.
And it can lead to stagnation. The latter didn’t happen yet
I could argue that it already did when Google abandoned JPEG XL.
Perfect time to move to Vivaldi, Brave, Librewolf, etc etc that wont be following suit. (yes the list does also include Firefox…but they bought an ad company and in my opinion are now compromised)
All Chromium based browsers are implicitly accepting money from an ad company because Google makes Chromium.
Plus having any rendering engine have a monopoly is terrible for the web long term.
Yep. Hey, maybe Ladybird will develop into a nice fourth option long term. As far as I know it’s just Chromium, Mozilla, and Safari being actively developed. (I forget the names of their internal rendering images, I think blink, gecko, and webkit but I’m not sure.)
I highly recommend waterfox
Wait what? LOL
Firefox is compromised because Mozilla bought an AD Company but Brave, an AD Company is not? Brilliant.
This can be problem for Firefox and Chromium based Browsers, too. If the Website decides that Manifest v3 is mandatory to visit their site, they can block any access from Browsers with v2 running in the background easier than before.
Websites don’t get to see what addons are you running
Luckily the first link is for a deprecated property that returns a hard coded list for compatability reasons, and the other two are extension apis that random websites can’t access.
Besides, with uBO (or a custom addon or userscript) you can replace the value of that list, for all sites or selectively
Then I guess I simply won’t frequent those sites.
A site that does this is a site I’ll never visit.
The other 95% of all visitors will still want to see this page. If the most visited websites use such a blocking method, then most visitors will use Chrome.
This is why Google is a monopoly and needs to be broken up.
I mean. 95% of people uses, likes and tolerates shit I don’t tolerate. I don’t use said shit. My life has been shockingly fine that way.
Hopefully Firefox won’t follow.
Firefox currently has no plans to drop support for manifest V2. It also supports the WebRequest API in V3, so ad blocking would continue to work if they do discontinue V2.
Awesome!
