- Google is transitioning Chrome’s extension support from the Manifest V2 framework to the V3.
- This means users won’t be able to use uBlock Origin to block ads on Google Chrome.
- However, there’s a new iteration of the app — uBlock Origin Lite, which is Manifest V3 compliant but doesn’t boast the original version’s comprehensive ad-blocking features.
Not trying to troll or anything, but what can Chrome do that Firefox cannot?
I’ve always felt like Firefox has more useful features like screenshotting, etc.
I only break out Chrome(or Edge) for two reasons:
One is access to serial ports to flash ESP devices, or update the firmware on my XR glasses. Firefox can’t do that.
The other is to automate Twitch drop collection. The addon I found to reload broken streams and collect drops while I’m at work only has a Chrome version.
I really hope ff gets WebSerial support.
The question is, is it gonna have a Manifest V3 version?
Looking at it, seems not. Google store page says it doesn’t follow best practices and may soon no longer be supported. AFAIK it’s a single dev hobby project so this might be the end of it. Ah well. I’ll just no longer have as many free skins for games.
Yeah, that FOMO is a bitch. I had to break myself of obsessively clicking for drops for games I don’t own or haven’t been playing.
Even if it didn’t have superior functionality, I’d still support & use firefox over chrome just because I don’t care how fast the sports car is: if it’s not going where I tell it to, I ain’t gettin’ in.
Last time I checked: tab groups. Yes there are extensions for it, but all the ones I tried were either really over complicated or buggy. Chrome tab groups are pretty simple and seamless to use.
But I’m going to have to figure something out because I’d rather lose tab groups than ad blocking, so I’ll have to switch to something.
Didn’t know about those in Chrome. Sounds good, though I’ve always just grouped my Firefox tabs by having a browser window of tabs per logical group
Some websites intentionally break Firefox for some reason. I’ve had numerous issues on Firefox which were resolved by switching to Chrome. These could potentially be fixed by a User-Agent string change, but instead of dealing with it I switched to a Chromium based browser.
What if we stop using User-Agent altogether? It would increase privacy and prevent browser discrimination. Too bad for the Analytics services, but after all… who cares?
Ding ding. This header is bullshit and only exists to exploit users.