I don't think I can go back to the internet without uBO+uMatrix. On a related note, why doesn't Chrome for Android have extensions? I get the sense it's because it was more strategic to ban extensions entirely than to allow ad blocking on mobile.
Google proposes changes to Chromium which would disable uBlock Origin
521–530 of 779 posts
Re: Google proposes changes to Chromium which would disable uBlock Origin
#522Earlier quoted context omitted.
> Chrome made web browsing/dev pleasant like Firefox/Firebug did and it really took off being based on Webkit like Safari which also worked well on mobile. This is the big one for me. When I'm not developing I actually prefer to use Safari-- I like it's interface better and it feels more at home in macOS. It's "good enough" too. What I'm really a user of is the Chrome Dev Tools. Firefox's are looking quite solid late…
What I'd love is to have Firefox dev tools functionality in Chrome. Firefox highlights the edge lines of the selected element automatically, and in all directions (if I recall correctly). I have to use an extension – VisBug – to achieve that in Chrome. There's also the fonts window, which lets you in on what fonts are used on the page, and lets you modify the selected element's font settings – size, weight, slant/ita…
Re: Google proposes changes to Chromium which would disable uBlock Origin
#523Earlier quoted context omitted.
But the design document only mentions retaining the old API for features that aren't possible with the new API, such as onAuthRequired. So it would still cripple uBlock
I really like the point the uBlock maintainer's make: "Extensions act on behalf of users, they add capabilities to a user agent , and deprecating the blocking ability of the webRequest API will essentially decrease the level of user agency in Chromium, to the benefit of web sites which obviously would be happy to have the last word in what resources their pages can fetch/execute/render."
That said, we should all fight for changes that let extensions like uBlock maintain feature parity.
Disclaimer: I'm both a Chromium developer and a uBlock Origin user and speak only for myself.
Re: Google proposes changes to Chromium which would disable uBlock Origin
#524Earlier quoted context omitted.
> Firefox is really the only thing preventing a complete web browser monoculture WebKit?
I use Safari as my preferred browser and I'm really happy with it, it's become a lot faster with each update, noticeably so. But I don't trust Apple any more than I trust Google to fight for a free Internet. We need an open browser.
Re: Google proposes changes to Chromium which would disable uBlock Origin
#525Re: Google proposes changes to Chromium which would disable uBlock Origin
#526Earlier quoted context omitted.
> For one, Apple defends ... It's fairly likely that's just PR. They're a US headquartered place, so would have to comply with NSL's (etc) just like every other US company.
Yes, they have to comply with NSLs. Difference though is the level of data they harvest on you. Google's business model requires they harvest as much as possible and in a way they ensure they can read it. Further, the bigger risk to most users is not NSL's, it's having some dodgy ad-corp buy your data and sell it to even dodgier companies.
And banks and insurances for credit ratings. And for screening companies, that are contracted to evaluate your job application on basis of your purchases, locations and so on
Re: Google proposes changes to Chromium which would disable uBlock Origin
#527Another reason to be glad that Firefox is still standing.
I really just don't understand the obsession with Chrome, especially in hacker communities. Sorry Google, I feel "icky & gross" when I use you.
Re: Google proposes changes to Chromium which would disable uBlock Origin
#528Earlier quoted context omitted.
Its not a free market
It's not a free market, so let's make it less of a free market by getting the government involved. That's the plan, right?
Re: Google proposes changes to Chromium which would disable uBlock Origin
#529Quote from the linked design doc: The current webRequest API allows extensions to intercept network requests in order to modify, redirect, or block them. It is frequently used by content blockers. Currently, with the webRequest permission, an extension can delay a request for an arbitrary amount of time, since Chrome needs to wait for the result from the extension in order to continue processing the request. The basi…
Re: Google proposes changes to Chromium which would disable uBlock Origin
#530Firefox exists, it works well, and it doesn't fuck its users to help advertisers. If Google manages to push it out of the market we'll be stuck with a garbage browser built by an ads company.