To my knowledge the YouTube API doesn't ban users for excessive use of the API, it just throttles them temporarily.
The exact throttling values are not posted publicly, but there are multiple third-party apps using the YouTube APIs successfully, so I expect the limits are high enough for a standard client to work without problems.
---
If Microsoft wrote a TOS-compliant YouTube app and put it in their app store, but it was written in a way that bumped up against the quota limits, I'm sure they and Google could work out some way to grant them more quota.
>If Microsoft wrote a TOS-compliant YouTube app and put it in their app store, but it was written in a way that bumped up against the quota limits, I'm sure they and Google could work out some way to grant them more quota.
MS has been requesting API access since three years, so I think there was no amicable resolution and MS was forced to do this.
From their statement:
"We’d be more than happy to include advertising but need Google to provide us access to the necessary APIs," says a Microsoft spokesperson.
1) Requesting Google design, implement, and publish a set of new APIs specifically to support a particular low-population platform owned by a self-vowed enemy of the technology stack Google is built on.
2) Requesting Google increment a few numbers in a database somewhere.
To my knowledge the YouTube API doesn't ban users for excessive use of the API, it just throttles them temporarily.
The exact throttling values are not posted publicly, but there are multiple third-party apps using the YouTube APIs successfully, so I expect the limits are high enough for a standard client to work without problems.
---
If Microsoft wrote a TOS-compliant YouTube app and put it in their app store, but it was written in a way that bumped up against the quota limits, I'm sure they and Google could work out some way to grant them more quota.