News for hackers. Stuff that matters.
Re:Snapjoy’s Flickraft Promised To Rescue Flickr Photos — Un... by jseliger on Tuesday February 07, 2012 @07:50PM (#3564451)
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.

Re:Snapjoy’s Flickraft Promised To Rescue Flickr Photos — Un... by dangrossman on Tuesday February 07, 2012 @07:53PM (#3564459)
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.

Re:Snapjoy’s Flickraft Promised To Rescue Flickr Photos — Un... by jpren on Tuesday February 07, 2012 @08:13PM (#3564522)
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.
Re:Snapjoy’s Flickraft Promised To Rescue Flickr Photos — Un... by estel on Tuesday February 07, 2012 @07:53PM (#3564460)
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.