Google To Block Local Chrome Extensions On Windows Starting In January

An anonymous reader writes "Google today announced it will block local Chrome extensions starting in January, but only on the Windows platform. This means that next year, Windows users will only be able to install extensions for the company's browser from the Chrome Web Store. The changes will affect both Chrome's stable and beta channels on Windows. Google says it will continue to support local extension installs on its Dev and Canary channels, as well as installs via Enterprise policy. Chrome apps are not affected at all and will continue to be supported normally."

Comments

Or, of course extensions that google doesn't like.

[queazocotal]

For example, YouTube downloaders-

I stopped using Chrome

[Anonymous Coward]

I stopped using Chrome because it's extensions were not up to par with Firefox addons.
And now I feel less inclined to use Chrome at all.

Ugh

[The MAZZTer]

I use an extension to download videos from YouTube. Those tend to be blocked from the Web Store, so you have to install them manually from other websites (this is the bit that is getting blocked). I hope there is at least a command line switch left in to disable this behavior! It's very "walled garden" and I don't like it.

BTW, the summary says "local extensions" but that is incorrect. It just blocks non-Chrome Web Store web extensions. Extensions you are actively developing and load via "Load unpacked extension" will still work.

Actually, that might have to be the fix for my YouTube extension I use. Oh well.

Walled Garden: One brick at a time....

[EvilSS]

Did Google recently buy a brick factory because they seem to be trying to slowly build a wall around their not-quite-as-open-as-it-once-was garden. Between this and some of the stuff they are pulling with Android (Play Store, API lock-ins) and Chromecast they seem to be all about turning down the openness lately. Come to think of it, that seems to be a trend (Skype, Twitter APIs off the top of my head, then of course that fruit company) lately.

Re:Walled Garden: One brick at a time....

[nurb432]

Don't forget moving nearly all their stuff to the new 'Google play framework'... and all the internal hooks it brings with it, just to read mail or send a message..

Google has run off the track.

Non-issue

[YodaDaCoda]

I suspect that this is less about blocking YouTube downloaders, and more about blocking those extensions that appear after not un-checking the box on programs downloaded and installed from the internet. I.e. it's more for the protection of grandma who wants to download a pretty solitaire app than it is for stopping little Johnny downloading his music videos of Miley. If you're smart enough to follow a few simple instructions and install a local extension, you're smart enough to follow a few simple instructions and install the Dev channel of Chrome first.

Re:Or, of course extensions that google doesn't li

[fuzzyfuzzyfungus]

If that were the motivation, would they not also do this on the Mac?

This is about _fucking_ annoying windows malware repeatedly reinstalling chrome extensions.

The fact that they are not breaking the capability on 'enterprise' policy installs suggests the same.

Incidentally, even if you aren't on a domain, this should mean that it isn't exactly rocket surgery to install the 'blocked' Chrome extensions. Winkey+r, gpedit.msc, import the chromium policy templates, modify 'ExtensionInstallForcelist' to taste. Game over.

Re:Or, of course extensions that google doesn't li

[Severus Snape]

In the store. Google made some changes to Webkit a while back to improve Adblock, before Adblock used to still have to download the ads, then block them. Some changes Google made allowed the ads to be blocked before the ads were fetched.

Re: Or, of course extensions that google doesn't l

[behrooz0az]

shushsh, the hosts file guy may hear you.