<![CDATA[Gizmodo: not being evil]]> http://tags.gizmodo.com/assets/base/img/thumbs140x140/gizmodo.com.png <![CDATA[Gizmodo: not being evil]]> http://gizmodo.com/tag/notbeingevil http://gizmodo.com/tag/notbeingevil <![CDATA[Google Wants to Install Servers at ISPs, Not So Sure About That 'Net Neutrality' Thing After All]]> The Wall Street Journal reports that Google has has approached ISPs with a plan to install servers within their networks, providing a "fast lane" for the famous supporters of net neutrality Updated 1:30p EST

On the issue of net neutrality, the project, tellingly called "OpenEdge", seems to indicate an about-face on Google's part. According to an extant Google Help page, the company's official position is as follows:

In our view, the broadband carriers should not be permitted to use their market power to discriminate against competing applications or content. Just as telephone companies are not permitted to tell consumers who they can call or what they can say, broadband carriers should not be allowed to use their market power to control activity online.

This was posted around the time that Google was lending its considerable influence to fighting the S.2686 Telco bill, which threatened net neutrality. In a letter opposing the bill, Google CEO Eric Schmidt said:

Today the Internet is an information highway where anybody – no matter how large or small, how traditional or unconventional – has equal access. But the phone and cable monopolies, who control almost all Internet access, want the power to choose who gets access to high-speed lanes and whose content gets seen first and fastest. They want to build a two-tiered system and block the on-ramps for those who can't pay.

Pretty clear, right? Then how does Google justify installing ISPs to host their content at higher speeds than other content? While it is easy to see how faster Google and YouTube access might be appealing to Google and consumers, it's clear that the company would have to pay for such preferential treatment, a practice which runs directly counter to their previous stance.

A likely defense would be that, in the case of OpenEdge, ISPs wouldn't be throttling other traffic, just accelerating Google's traffic. That would be true, but not the point. The system wouldn't adversely affect existing services or threaten P2P traffic, but it would be creating a tiered internet, which—no matter how it's packaged—is the greatest fear of proponents of net neutrality. When pressed on the issue, the company simply indicated to the WSJ that "other companies such as Yahoo and Microsoft could strike similar deals if they desired." Coming never: fast-tracked Giz, courtesy of Comcast.

UPDATE:: Epicenter reports that Google responded to WSJ's article, calling it confused. They claim that their OpenEdge, which uses a technology called edge caching (already in use by Amazon), does not contradict their policy on net neutrality. Rather, they claim it only improves the end user experience by colocating a server to minimize the distance between their content and the user, thus speeding up the time it takes to load content. Google feels that ISPs and content providers working together to improve performance is not the same thing as ISPs only making content available for a select audience. [WSJ]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5109961&view=rss&microfeed=true
<![CDATA[Google Has a Remote Kill Switch For Android Apps]]> Just after the dust finished settling on Apple's controversial admission that the iPhone has a remotely activated kill switch for applications, Google has plainly stated in their Android Market terms of service that they've got one too. Like Apple's solution, Google's remote kill switch is ostensibly intended to protect users in cases of malicious apps or privacy violations, but will undoubtedly draw fire from users who want — and in the case of Android were pretty much promised — ultimate control over what applications they keep on their phones.

While Apple reluctantly acknowledged the existence of their kill switch only after it was discovered by developers, Google has been relatively upfront about Android's. They've even laid out plans for reimbursing users whose paid apps (which aren't even available yet) are recalled. And as ComputerWorld notes, a kill switch makes a little more sense for Android, as their applications aren't really vetted in any meaningful way before showing up in the app store.

Retroactive vetting, though, is still vetting, so Android's App Market may be a little more like the App Store than we originally thought. As before, we'll just have to wait for the final verdict on this one from preeminent kill switch expert Stephen Colbert. [ComputerWorld]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5064357&view=rss&microfeed=true