If you have uBlock Origin, you might notice Chrome automatically disabling the extension.
Google Chrome has begun to phase out uBlock Origin. The developer of the free ad blocker, Raymond Hill, recently reposted a screenshot that shows Chrome automatically turning off uBlock Origin because it is “no longer supported.”
The change comes as Google Chrome migrates to Manifest V3, a new extension specification that could impact the effectiveness of some ad blockers. uBlock Origin has launched uBlock Origin Lite, which uses Manifest V3, in response to the transition. However, you have to manually install the extension because it’s “too different from uBO to be an automatic replacement,” according to a FAQ Hill that posted to GitHub.
Nothing a user agent spoofing extension can’t fix.
Also, if anyone has concerns about Firefox there are some really interesting forks.
Zen has been my go to for a couple of weeks.
Why is that? Folks aren’t going round writing user agent parsers to maliciously disable functionality in Firefox. They’re just writing bad code that doesn’t work on anything but the browser they use.
I use Firefox mainly because I don’t trust Google and at work it ensured at least one of us sees bugs that chrome users don’t.
They are.
Not maliciously, but out of laziness.
I regularly see “you need chrome to use this site”.
Would love to see examples of this, I’ve never seen it (since 2000 or so)
Issue is that some sites just refuse to work saying you need to install a supported browser. Changing the user agent fixes this.
Would love to see an example of this
When I say “aren’t supporting” I mean “not testing”. These sites are broken.
All Firefox forks in existence are merely soft forks. They’re not committing code, they just compile with different flags and configure.
Not entirely accurate.
Zen brings a number of additions that even the Mozilla team have taken note of regarding features they hope to implement down the road.
Ref: (ff engineer taking about zen’s implementation - that’s not enabling feature flags) https://news.ycombinator.com/item?id=41307555
That link is talking about tabs?
That’s just css. Every soft fork messes with that. You can yourself in user.css
The big deal with tabs is getting UX right. It’s more about how it looks and whether it’s intuitive, rather than implementation.