Some observations about extension interaction with ScriptSafe in Google Chrome through other extensions, sometimes redirects from HTTP Switchboard and uBlock comes to be established earlier and I get a ScriptSafe extension alert from inside Google Chrome Managment (orange alert).
In the Golden Age of Tracking and Surveillance via your browser adblocking has many aspects of a reargard tussle.
First users protected themselves against cookies, in came more stealthier cookies and other ways like web beacons and even more devious ways.
Now we are in a phase where the adlaunching comes hard coded into the web browser outlay (tiles in firefox) because the average user won't avoid that by changing the about:config settings for json, or via special firewall settings.
When ads are your core business it is hard to offer a browser that is a user friendly browser in these respects like the Google Chrome browser.
This would not be such a problem when there weren't millions and millions of malware ads that put the user at risk and Google has to stop.
This makes our look upon adblocking quite differently - adblocking is an integral part of the average user protection.
Adblocking necessare est! (Adblocking is a neccesity!)
I also observed that extensions work differently when I work Google Chrome inside sandboxie. Also a problem forms how Google protect the browser from extension interference, some lower layers in the browser cannot be reached by developers, as Google does not allow it, so other ways around that should be sought or other ways to get the required outcome. HTTP Switchboard seems a clever concept here.
That a browser is meant to feed you ads like your parents tried to fed you cod liver oil in the evening in the 50's (open your mouth and hold your nose, now swallow) is shown when you find complete privavcy protection with no-script actively working a browser in tor. The browser may stop page loading and Google may start to feed you continuous captcha's to establish whether you are human (they apparently lost your tracking and monitoring trace slightly). Another way of pestering browser users that use tor is the continuous captcha's being thrown up from websites that come to us via CloudFlare. So all monopolists apparently are into the same game here.
Another example Google does not like adblockers was to block ABP app out from their Android platform where they had enough monopoly to dare and take such a position - take it or leave it. Existing Adblock users even had to change their smartphone proxy settings to make ABP would not stop functioning.
I could even find myself allright with the so-called non-intrusive ads, but I know malvertisers won't leave them alone, because they are a royal unobserved way into the browser (Google cannot guarantee the ads will be non-malvertised and there are more malcreants malvertising than Google's way to stop them or willingness to stop them, because cheap money from clean advertising and clickfraud SEO spam or malware injected ads is part of the same income stream).
polonus
