23rd
find2follow featured at n.27 — “Twitter is currently the hottest web service, and along with it comes a large flock of what is known as Twitter apps or mashups. It took me a while before I was able to filter out the simplest ones out there, and I’m happy today to share with everyone the 105 Twitter apps I found to have a clean and minimal design that compliments the simplicity of their single function.”
We’ve just released some minor improvements on the API. Firstly, two HTTP status codes have been included: 405 (Method Not Allowed) and 406 (Not Acceptable). The idea is to facilitate debugging, and to provide more detailed output.
Secondly, the API now expects an HTTP header called ‘Accept’, which is used to specify the media-type that is acceptable for the response. The find2follow API currently accepts JSON (‘application/json’), but new types might be included in the future.
That’s it. We’ll keep enhancing our API, so that you can develop your app on top of a reliable and robust platform. Check out the super-brief API specs.
So find2follow took off, and it’s been crazy. We’ve experienced some side effects from the recent user base growth, which is exactly the sort of headache we were looking for :)
find2follow used to be constrained by Twitter itself, so unfortunately some of you came across the following message: “We’ve reached our hourly limit given by Twitter”.
Therefore, we got in touch with the guys at Twitter, and the good news is that we’ve been whitelisted. It means that our current hourly limit has increased a lot. In fact, I’d say that constraints are gone!
If you were one of those who got that message, you may consider yourself lucky, because nobody will ever see that message again! :)
Thanks for trying find2follow out!
share questions, ideas, problems, and praises with the dev team as well as other users
Listening to Kings of Leon while coding new features