Re:Show HN: A Chrome extension to get around the WSJ paywall
by ToastyMallows on Wednesday July 30, 2014 @02:48PM
(#8110188)
How do developers test their own extensions then? Surely there must be a way around this.
EDIT: I just followed the installation instructions and it worked fine. It says "Not From Chrome Store" but it's still enabled.
Re:Show HN: A Chrome extension to get around the WSJ paywall
by j0k3r on Wednesday July 30, 2014 @02:51PM
(#8110206)
You need the source code of the extension and not the .crx to be able to load it and use it as a developer.
Re:Show HN: A Chrome extension to get around the WSJ paywall
by CaveTech on Wednesday July 30, 2014 @02:52PM
(#8110213)
If you install via "load unpacked extension" you can get around it.
On recent versions of Chrome you cannot install any non webstore CRX, developer mode or not.
Re:Show HN: A Chrome extension to get around the WSJ paywall
by ToastyMallows on Wednesday July 30, 2014 @02:54PM
(#8110221)
What version of Chrome? I'm using 36.0.1985.125 and it worked just fine.
Re:Show HN: A Chrome extension to get around the WSJ paywall
by phr4ts on Wednesday July 30, 2014 @03:12PM
(#8110326)
When you restart, it would be disabled. There are two ways around the block. The first has been mentioned above - load unpacked extension.
The second is much more of a hassle and didn't work for me. It involves using group policy to whitelist the extension.
Re:Show HN: A Chrome extension to get around the WSJ paywall
by ToastyMallows on Wednesday July 30, 2014 @03:38PM
(#8110445)
Ah ok, I had to kill all the background processes to really "restart" Chrome. Thanks.
If you ask me, I think this was a completely unnecessary and definitely self-interested move from Google, but since most here on HN bought Google's narrative and thought it's a good idea "because security" (with zero data to back it up), and didn't speak out against it, now we're stuck with this.
Having to enable Developer Mode and drag and drop an extension was more than enough "security". They didn't have to limit them to the Chrome store, just like they don't limit much more complex and more dangerous Android apps from being installed from other places, when you check the Unknown sources button.
Now try to add this extension in the Chrome store, and watch how you're promptly deleted by Google. And now hopefully people will understand why Google's latest move was completely self-interested and also unnecessary security wise. It was designed specifically to reject this sort of extensions from working on Chrome.
One more thing to ponder about: Even Apple doesn't completely ban native apps from running from other sources. It still gives you the option to install Mac apps from other sources. Chrome doesn't (anymore).