31–40 of 215 posts
Earlier quoted context omitted.
Developer effort.
Don't underestimate the power of spite.
I don't want to pile on here but everyone who used Chromium while pretending they weren't supporting google's Chrome monopoly, pretending Chromium was something else, are getting the only outcome that was possible. It was entirely predictable from the start and if you play stupid games you win stupid prizes.
And the stupid prize is what? You might have to use a different browser? Doesn't seem that serious to me.
Earlier quoted context omitted.
Blocking is detectable. uB doesnt block, it shims its own version of js.
I'm not sure what you mean.
I don't want to pile on here but everyone who used Chromium while pretending they weren't supporting google's Chrome monopoly, pretending Chromium was something else, are getting the only outcome that was possible. It was entirely predictable from the start and if you play stupid games you win stupid prizes.
And the stupid prize is what? You might have to use a different browser? Doesn't seem that serious to me.
Earlier quoted context omitted.
I'm not sure what you mean.
If you block third party javascript files (e.g. google analytics) other code required for the website to function correctly might fail, since it relies on that third party javascript. So uBlock doesn't block certain javascript files, and instead replaces them by its own version which contains dummy functions that avoid those errors.
I don't want to pile on here but everyone who used Chromium while pretending they weren't supporting google's Chrome monopoly, pretending Chromium was something else, are getting the only outcome that was possible. It was entirely predictable from the start and if you play stupid games you win stupid prizes.
It's not like no one was making warnings about this.
Earlier quoted context omitted.
Don't underestimate the power of spite.
Spite is at times my main source of motivation, and still leaves me physically uncapable of following the rate of breakage of upstream Firefox (i.e. I cant keep my patches up to date), which I'm assuming it's actually a more sensible upstream when compared with Google.
Chromium team has not commented on this bug with 650+ stars (within top 10 https://bugs.chromium.org/p/chromium/issues/list?sort=-stars... issues) in months
As a proxy extension developer, this is absolutely maddening. We're forced to choose between auth-less open proxies (bad), or baking in a wacky authentication scheme through a side channel (also bad). MV3 drops in 2.5 months, and will leave tens of millions of proxy extension users unable to use products they paid money for. This is all on top of the many other issues with MV3 that Google is pushing under the guise o…