Suspending an API key after that user exceeds a published rate limit sounds perf... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		dangrossman on Feb 8, 2012 \| parent \| context \| favorite \| on: Snapjoy’s Flickraft Promised To Rescue Flickr Phot... Suspending an API key after that user exceeds a published rate limit sounds perfectly reasonable. We have no reason to believe it wasn't automated and temporary, yet. That's not "lame". The limit was 3600 API calls per hour. They moved 125,000 photos per hour. I don't know how many calls that involves, but it appears well over the limit.

jpren on Feb 8, 2012 [–]

You can pull up to 500 photos per flickr API call, so it's possible to fetch up to 180,000 photos per hour while staying under the limit.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact