Chrome API Update Will Kill a Bunch of Other Extensions, Not Just Ad Blockers (zdnet.com)
An anonymous reader writes: A planned update to one of the Google Chrome extensions APIs would kill much more than a few ad blockers, ZDNet has learned, including browser extensions for antivirus products, parental control enforcement, phishing detection, and various privacy-enhancing services. Developers for extensions published by F-Secure, NoScript, Amnesty International, and Ermes Cyber Security, among others, made their concerns public today after news broke this week that Google was considering the API change. Furthermore, efforts to port NoScript from Firefox to Chrome are also impacted, according to the plugin's author, who says the new API update all but cripples the NoScript for Chrome port.
Before jumping ship, it's worth reading the actual thread discussing this change: https://groups.google.com/a/ch...
Google staff are participating. They are talking about the need to keep the old API around indefinitely, perhaps with some limitations on functionality. The purpose of the proposal is to gather feedback from add-on developers about what functionality the new API doesn't offer and needs to be kept in the old API.
In particular, they recognize that for privacy reasons it's important for users to have a 100% guarantee that certain things are blocked and not merely hidden, which is the main performance issue at the moment.
Also, the developer of AdBlock Plus chimed in to dispel the myth that it's got something to do with them. They point out that AdBlock is affected by the change as well.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Before jumping ship,
Nah, just jump to Firefox.Firefox is a fine browser, and it's better to not have a browser monoculture.
"First they came for the slanderers and i said nothing."