NoScript extension officially released for Google Chrome
zdnet.com
zdnet.com
1) Propose API changes with blatantly obvious impacts on some of the most popular extensions. Include no explanation of how these extensions can rationally adapt to these new APIs and provide the same or adequately similar functionality.
2) Don't bring any timing data to justify the performance claim that ad blockers are taking an irrational amount of time implementing their content filtering. When others run these same tests they find no performance issues.
3) Characterize any strong reactions to such a suggested change as inappropriate. Feign surprise and dismay at the fact that such reckless API changes, which would drastically change the status quo on the web, are invoking.
4) Condemn those who didn't react the way you expected when you threatened to vastly change their web browsing experience for the worse. This helps diminish user input in the future, by tying everyone with honest opinions to those who express their opinions in an inappropriate or unprofessional way.
5) Act insulted when people point out that your employer, who is in control of the situation, happens to financially benefit from the changes.
The above experience was so distastefully handled across the board, I really think it justifies a unified and community supported "ungoogled-chromium" project without any of their trademarks in the name. That way we the users of the web can determine our relationship with the browser. It's the user's agent, not the browser vendor's agent.
But most importantly, use Firefox with containers and uBlock Origin.
PS. Despite the above, kudos on the port of NoScript. Never give up, never surrender.
Their behavior is much of a politician trying to do something while trying to hide their end-goal.
Edit - This is a good example of what I'm talking about: https://i.imgur.com/Lwr3xhY.png
You also have more fine-grained control where the matrix interface allows you to white-list specific domains (and you can select whether you want JS/Frame/cookies, etc per domain). If you save your white-listing, that will always be remembered even across other websites. So for example, if I were to white-list twitter.com for js/frame and save that, then if I visit another site that embeds links to twitter widgets, those will work because you've already white-listed twitter.
Umatrix does take a bit of effort initially when you start with a blank slate, but over time, it works fairly well and I feel a lot more comfortable browsing the web with it.
Still pisses me off the integrated browsing tab behavior in apps. I REALLY want links in firefox and twitter, etc to open in MY browser of choice.
I've been test-driving Mozilla's experimental Fenix browser. It already supports Tracking Protection (which happens to block most ads as well) and it's in general a really nice browser, but I can't stand using it for anything that isn't basically Wikipedia, because of those annoying Cookie notices.
Previously, I had used dns66 and other similar VPN-based solutions (since I'm not rooted), but they all had various problems, that over time became really annoying to me.
FF is a breath of fresh air on mobile. Google take note.
Actually he is dumping source in the releases but no history or link to where he forked chromium (there may be an artifact in the source tree that would help however) -
Can't even directly diff against chromium.
I guess thats true
XDA indicates "progressively open source" whatever that means https://forum.xda-developers.com/android/apps-games/app-kiwi...