Google Chrome Will Block All NPAPI Plugins By Default In January
An anonymous reader writes Google today provided an update on its plan to remove Netscape Plugin Application Programming Interface (NPAPI) from Chrome, which the company says will improve the browser's security, speed, and stability, as well as reduce complexity in the code base. In short, the latest timeline is as follows: Block all plugins by default in January 2015, disable support in April 2015, and remove support completely in September 2015. For context, Google first announced in September 2013 that it was planning to drop NPAPI. At the time, Google said anonymous Chrome usage data showed just six NPAPI plugins were used by more than 5 percent of users, and the company was hoping to remove support from Chrome "before the end of 2014, but the exact timing will depend on usage and user feedback."
Oh, this doesn't affect AdBlock? Don't care then.
If I knew which 6 NPAPI plugins were used I'd know if I cared or not.
So, which plugins does this really affect?
An honest question, why use Chrome when you can also use Chromium and not be 'the product'?
I'll stick with Firefox.
"The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
Just wait until da po-po guy is let off the hook. The city will come unglued.
People who use Cisco WebEx, which uses one of those "top six NPAPI plugins," are in for a rude surprise.
What's amazing is that this 1996-era hack for extending the functionality of the Netscape browser, in a rather kludgy and unsafe way, still exists at all in 2014. I took a class at the Netscape office in Mountain View in 1997 to learn how to write NPAPI plugins and thought then that it was an ugly hack that deserved to go way soon, though I was glad it existed to solve my immediate problems. Not only did it not go away (though MS removed NPAPI support for IE a long time ago), nearly all major browsers today still support it.
Good for Google for deprecating this crap. Firefox (which is to some degree a descendant of Netscape) has also been reducing its support, per the WP article.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
I know NPAPI wasn't exactly the most elegant thing, but at least it was supported by a few major browsers. Are there any good plugin API alternatives that are cross browser? Or is everyone having to implement a version of the plugin for each browser using whatever API that browser has decided to support?
I've seen a bunch of ssl issues with Chrome recently, and canary is rapidly going down hill for webpage compatibility. In fact recent versions of Chrome have been so bad at corrupting local certs that our network admin has started blocking it for unprivileged users.
So unless Google fixes Chrome's problems, it's days are numbered.
I have been trying to like Chrome ever since they first released it. I have failed. I just don't like the interface. Perhaps because I have been using the web for a long time and I really liked Netscape back in the day. I do use Chrome in places that my heavily secured Firefox won't go. That is pretty rare though.
So, I don't care what they do with Chrome, because I don't use it unless I have to. Mozilla just works better for me. Never know if that will change someday, but it hasn't yet.
Most grey market shitware that's "technically" not malware (Aka stat tracking/ad inserting 'browser bars') drops a plugin based piece of garbage in to every browser it can find.
Love to see that shit blocked by default.
In fact, I hope google explicitly and aggressively blocks anything not signed and delivered from the chrome web store.
You need something not approved by google? Run chromium. That's what it's there for.
For the other 99.99% of the internet browsing public, letting google wall up the garden a bit really is the better option. Google aint perfect, but they're a lot more trustworthy than the drive-by downloads that get spammed all over their facebook walls.
Interesting. So when will they stop pushing PPAPI? It's already obsolete anyway with all the stuff that's been put into "HTML5" lately. It'd be nice for Google to look less like they're trying to replace the web with their own version nobody else cares about except diehard Google fanboys.
They're ending support when it literally annoys just a handful of developers. That might optimize the benefit of dropping support. Any later and they're expending too much effort for the hold-outs. Any earlier and they're shoving too much burden on an active legacy community. They gave plenty of warning too.
I'm not some Google fan-boy. There are plenty of things they do wrong; but credit where due.
For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
NPAPI plugins (or at least Unity) already don't work on the Mac version of Chrome
CATS/Diebold '08- All your vote are belong to us!
again..
Flash does not use that API anymore?
I remember when the problem of web video was finally solved for like a couple monthes, at least for me. WMV video plugin would reliably install and play full screen video on a modest computer. But instead, flash video replaced it and tripled the CPU requirements, and it works but this is shit.
The web would be better if we had followed the route of a NPAPI video plugin, we'd have Youtube that works on a Pentium II and 128MB RAM. Running three of them would not make a 2GHz single core computer crumble.
>>> Google said anonymous Chrome usage data showed just six NPAPI plugins were used by more than 5 percent of users
Yes, Chrome browser does call home by default.
I believe Google dropped NPAPI support in Linux for version 35 onwards. This *immediately* broke all Java applets (as far as I know, there's no PPAPI Java plug-in), which wasn't great for sysadmins using Java VNC applets (yes, I know about noVNC, but not all Web UIs have moved to that) or F1 timing on formula1.com as a consumer example.
Google Chrome for Linux dropped support for NPAPI in version 35. This meant that if you use VMware, there's now no current browser which allows you to open VMware consoles via VMware vSphere/vCenter.
This is because of two related issues:
- vCenter needs Flash, but it has to be *recent* Flash (not 11.2 Linux Flash). Only option which provides recent Flash is Chrome;
- vCenter's 'launch console' add-in is NPAPI-based, so that won't work from Chrome version 35 onwards.
Therefore my VMware-managing setup on my Linux desktop is Google Chrome 34, pinned to prevent updating; and this is used only for local VMware management, not browsing.
I post this just for information and to rant about it yet again, but of course this is VMware's fault for relying on a deprecated architecture for plugins.
"If you think the problem is bad now, just wait until we've solved it." --- Arthur Kasspe
Just keep using vi dude, I know you can use it for email, calenders, docs, spreadsheets, ide, chat, etc...
Liberty freedom are no1, not dicks in suits.
Maybe they should block all malware plugins too. Honestly after running a small repair shop, I could name them off right off the top of my head. Block those assholes and turn it into a marketing thing to brag about security (security for stupid, careless people at least).
Bullshit.
Google wants complete and utter control of the browser and your internet usage.
Fuck the googletron.
Can't watch Slingbox without using their plugin, which uses NPAPI. They seem unwilling to update any software...which means I'll have to boot up IE just to use Slingbox.
That is after they make me watch a 15 second advertisement to watch TV I pay for on hardware I pay for on the only valid viewing option on my PC.
why not just close chrome like other google projects. :)