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

1) That's certainly lame on the part of Flickr.

2) I find it odd that Snapjoy is offering this at a time it isn't accepting new accounts: I clicked "sign up" and entered an e-mail address to be notified about when they're expanding.

3) I hadn't heard of Snapjoy before this story.



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.


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.


Why is it lame on Flickr's part to ban/suspend an API key exceeding the requests limit? I can entirely believe that this was automated.




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

Search: