Live data from Hacker News

The limits of Google’s openness

blogs.technet.com

71–80 of 303 posts

Re: The limits of Google’s openness

#71
post #15

M$: "Google also says that we are not complying with its 'terms and conditions.' What Google really means is that our app is not based on HTML5. The problem with this argument, of course, is that Google is not complying with this condition for Android and iPhone." Google's T&Cs that M$ is citing, it would seem to me, apply to third-party use of YouTube data. Since Google wrote the Android and iOS YouTube apps, this i…

> Google makes the rules for YouTube, and can therefore bypass them with impunity. M$ cannot.

Well, yeah. But for a company so heavily invested in HTML5 to demand another company apply it, while simultaneously not doing so themselves, is a little hard to stomach.

Re: The limits of Google’s openness

#73
post #40

A summary for those not following along at home: The Youtube app for Android is developed by Google The Youtube app for iOS is developed by Google The Youtube app for Windows Phone is developed by Microsoft, with some reverse engineering, at first not serving ads on purpose. It is easy to argue that a Youtube app for Windows Phone would be nice for WP users. It is also easy to argue that MSFT writing such an app woul…

>The Youtube app for iOS is developed by Google Except that the original iOS app was developed by Apple and Google had no issues with that

Can you cite a source for "no issue with that" ?

Re: The limits of Google’s openness

#74
post #35

It's my understanding that YouTube officially supports access via either a Flash applet or the HTML5 tag. Windows Phone doesn't support Flash[1], so the only option for writing a mobile app using the official API is to use HTML5. It's not obvious why using the HTML5 API is "impossible". Windows bundles a -capable browser; assuming IE's capable of playing either H.264 or WebM, it should be relatively easy to build a Y…

The experience you can provide with an HTML5 app are many times subpar as compared to a native app. Note how facebook abandoned their HTML5 app and went native.

Also note how sencha then went and re-created the new facebook app in html, showing that facebook was full of shit.

Re: The limits of Google’s openness

#75
post #47
post #28

Earlier quoted context omitted.

Do two wrongs make a right?

No, but Google doesn't owe Microsoft any favors.

I genuinely don't get this line of thinking. This isn't about Google or Microsoft, rather it's about the end user who is essentially a customer of both parties. IMHO, Google aren't just screwing MSFT, they are screwing users, which doesn't really hold with the image that they like to portray. It's actually rather spiteful.

Re: The limits of Google’s openness

#77
Disclosure: I am a Googler, though not working on anything remotely near YouTube. Obvious caveat: this is just my personal opinion.

> With this backdrop, we temporarily took down our full-featured app when Google objected to it last May

If I remember right, this full-featured app included features like:

1. Allowing users to download videos even when the content provider disallowed that.

2. Allowing users to not view ads even when the content provider specifically required ads to be shown.

3. Using YouTube's branding without permission.

I am but a lowly engineer and the actions of executives confuse me, but I don't see how Microsoft didn't realize the above was batshit crazy. I can only assume this is some sort of weird ploy.

YouTube's entire business model is about getting content providers to put videos up there so that people will watch ads to see them. If you let people take videos off the site, or just skip the ads, that breaks the fundamental business proposition.

This would be like me making an Android app called "Bing from Micrsoft" that let you perform bing searches but then stripped out all of the ads. Microsoft would shut that shit down, with good reason.

> When we first built a YouTube app for Windows Phone, we did so with the understanding that Google claimed to grow its business based on open access to its platforms and content, a point it reiterated last year.

"Open access to content" doesn't mean "ignore the requirements of the people who created that content". People make their livelihoods producing YouTube videos and the only way that money flows to those creators is because of ads. If you make a Windows Phone app that lets you watch Cooking with Dog without the ads, you aren't doing Francis any favors by giving out "open access" to his content.

(Yes, I did just imply that they are the dog's videos. He is the host, after all.)

Re: The limits of Google’s openness

#78
post #40

Earlier quoted context omitted.

>The Youtube app for iOS is developed by Google Except that the original iOS app was developed by Apple and Google had no issues with that

The original iOS app only showed videos that did not require ads. Microsoft's YouTube app used to work the same way, until they updated it to show all videos but still not show ads. EDIT: According to itafroma, the Apple-authored YouTube app for Apple TV will play all videos without ads.

> The original iOS app only showed videos that did not require ads.

That's not correct. The original iOS app played all videos, regardless of whether they were monetized, as long as the creator checked the "make available for mobile devices" option. It works the same with with the current Apple TV app: monetization options have no effect on videos' availability.

Re: The limits of Google’s openness

#79
Really annoying Google blocks IMs from other services now as well. Lots of people complain to me they can't IM Google users any more. Apparently Google removed server to server XMPP support, a standard open IM protocol, in favor of their own lock in protocols. Other products are following suit, Chromecast doesn't include support DLNA or other standards for example, but tries to force you to use Google proprietary stuff instead. In many cases this is a worse situation for users and only benefits Google by locking more people in and forcing more people to use services that aren't superior. Many people have their own media center or media server setups that are incompatible for example, like XBMC, a popular media center.

Re: The limits of Google’s openness

#80
post #15

M$: "Google also says that we are not complying with its 'terms and conditions.' What Google really means is that our app is not based on HTML5. The problem with this argument, of course, is that Google is not complying with this condition for Android and iPhone." Google's T&Cs that M$ is citing, it would seem to me, apply to third-party use of YouTube data. Since Google wrote the Android and iOS YouTube apps, this i…

> M$

Heureka! My timemachine worked and I'm back in the 90s!

Post reply on HN