To view parent comment, click here.
To read all comments associated with this story, please click here.
The point is that exist in spite of Google's efforts, and they constantly need reengineering to work again. It's far from a pleasant experience.
MetroTube has broken 2-3 times in the past year, and then earlier in 2011 for over a month. To say this is good enough, and then dismiss Microsoft's claims as petty is unfair.
But okay, I get it, you did your little OSNews hit job of the week. Good job.
Thom, you're desperately wrong on this! MetroTube is a hack which uses undocumented APIs to get access to youtube's content.
iOS and Android are given unrestricted access to the public APIs, but Windows Phone is blocked.
Microsoft have a 'MetroTube' available, but the reason they can't release it is because they're obviously under a lot more scrutiny and can't get away with what indie devs are doing.
You can't find documentation to make a fully featured YouTube client. I don't think you understand this.
Huh?
https://developers.google.com/youtube/
Edited 2013-01-03 05:41 UTC
Have you actually tried to use the API? Are you stupid? Is this entire article made up? Are the issues that third party Windows Phone and Windows Store apps have imaginary? Are you inebriated?
YouTube offers a SUBSET of APIs available, you CANNOT build a fully functional YouTube client using the public API because it is incomplete and only allows for superficial integration with the service.
If you had bothered to read the documentation (you didn't) or even bothered to try to implement the API (again, you didn't) or even did the slightest amount of due diligence (nope again) you'd know this is true.
This is what is truly infuriating, you're so interested in a fucking gotcha that you don't even take the time to do basic research.
Sorry to butt into the convo here, but:
Documentation to create a fully featured YouTube client:
- http://www.w3.org/TR/2012/CR-html5-20121217/
- http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-2...
- http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devne...
There's some other docs those ones depend on but that's pretty but the core of it right there.
Of course, most computing devices have at least a partial implementation already.
;)





Member since:
2005-11-29
OOXML and the network protocols SAMBA uses are open and documented standards/protocols.
YouTube is not. You can't find documentation to make a fully featured YouTube client. I don't think you understand this.