Forgot your password?

Comment: Re:Needed to stop anyway (Score 5, Informative) 153

by kav2k (#47398917) Attached to: New Zealand ISP's Anti-Geoblocking Service Makes Waves

A couple of points.

First, those restrictions have recently been kicked up a notch in ridiculousness. Some publishers now disallow gift copies in those "cheaper" regions - presumably, to stop such cross-region trading, but you can't even gift the game to someone within the region.

Second, it's important to remember that region restrictions are entirely up to the publisher. As far as I can tell, Steam more or less mandates cheaper prices for Russian region, but adding restrictions is entirely publisher's decision. For instance, no digital copy of a Valve game was ever subject to those restrictions (retail is another matter though). Most indies don't opt for regional versions.

Comment: Re:Developers? (Score 2) 225

by kav2k (#47105625) Attached to: Google Starts Blocking Extensions Not In the Chrome Web Store

So how do I develop extensions?

Like you always did. Developer mode did not change this time around.

Also, how do I run the custom extensions that are used in our company and should not be publically available?

Enterprise install policy is unchanged. If you can use it, you can use extensions from any source. Even NPAPI extensions, which are now banned from Store.

How about extensions that are installed with some hardware, like the one that makes Dymo labelwriters accessible from JavaScript?

It's probably not an extension, but a plugin. That's a bit different, but they will also be going away end of this year.

Comment: Re:Also in Chrome 33: Welcome to Walled Garden (Score 1) 125

by kav2k (#46356597) Attached to: Chrome 33 Nixes Option To Fall Back To Old 'New Tab' Page

Thanks for the reply.

I understand that there are several viable workarounds. Especially since on Windows, ChromeSxS actually works (hello, #38598), using unstable is relatively painless. But I can't shake off the feeling that you got a nice bonus of enforcing CWS TOS on the largest chunk of your userbase.

Non-Web-Store extensions never had auto-update to begin with. The only difference between loading unpacked and side-loading is that it's a bit trickier to install unpacked, and Chrome will warn you every time you start up.

This is simply not true. I've been an extension developer for quite a long time, and I've always hosted a beta version of my extension outside CWS, with auto-update, using update_url key in the manifest.

And that's why I had to scramble to move my beta version to CWS unlisted before 33 hit stable. If I missed the announcement, it would be slightly painful to recover.
I wonder though, if you've engineered the hard block of an extension to still look for updates. So that a user who had an extension blocked by this would later get the extension back if the developer submitted it to the webstore with the pem file.

Comment: Why NOT WhatsApp (Score 1) 280

by kav2k (#46322377) Attached to: Who's On WhatsApp, and Why?

I can tell you why I don't use WhatsApp.

While a competent mobile-oriented IM is a good idea in general, I intensely dislike the fact that they went with binding your account to your phone number. I juggle several SIM cards, and that's a no-no in WhatsApp's book.

I infrequently use Kik for the same purpose as WhatsApp, especially linking its detailed message delivery status, but their recent changes to TOS and embedding a browser in-app makes me wary to continue.

Comment: Also in Chrome 33: Welcome to Walled Garden (Score 4, Informative) 125

by kav2k (#46315163) Attached to: Chrome 33 Nixes Option To Fall Back To Old 'New Tab' Page

You think that's the real problem in Chrome 33?

Well, compare that to this fact: on Chrome 33 on Windows (and Windows only) all non-Chrome-Web-Store extensions are forcibly disabled and will not install anymore, with the exception of pushing them through domain group policy.

So, say goodbye to anything not blessed by Google, like extensions that allow "the unauthorized download of streaming content or media".
Unless you want to use the Dev channel as an official workaround, or are content with loading extensions unpacked, with no auto-update.

It's not like I don't understand the problem, I've seen rampant Chrome crapware on clueless people's computers. But this is heavy-handed.

He keeps differentiating, flying off on a tangent.