Here's an idea which may or may not work:
Write some javascript which detects when there may be an error (if
you're already using the json api on the client end that would be really
easy - otherwise you could look for common errors in the player itself).
When you detect it, get the javascript to send the video id to your
backend to report it as a potential problem - then your backend only has
to check the video ids that it already believes have a problem, and you
shouldn't hit the rate limit.
Tim Wintle
On Tue, 2011-09-20 at 15:21 -0700, Louis Alley wrote:
> Hello,
>
> I'm an engineer at Zimbio.com, an online entertainment magazine. One
> of our features allows users to post YouTube videos under content
> categories. Over time, many of these videos have become invalid,
> either because the YT user deleted the video, or the YT user was
> deleted, or the video violated some copyright. We want to improve the
> user experience so that all the videos play instead of just showing
> YouTube / Invalid.
>
> I'm writing a script to verify the good videos and throw out the bad
> ones. Here's the request I'm using:
>
> http://gdata.youtube.com/feeds/api/videos/' + YT.code + '?alt=json
>
> If I delay 5 seconds between each request, I still hit the rate
> limit. Even if each request was successful, at this rate it will take
> over two weeks to cull the bad videos from the database. Ideally this
> is a process we would run every 1-4 months. I can't find any good
> contact point to request an increase of my quota. What can I do?
>
> Thanks,
>
> Louis
>
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment