@john help.twitter.com/forums/10711/entries/15364 This says it's 1000 a day. It's still a lot, but easily broken with an application like this. I'm not sure if the API request rate also factors in to this, I always forget, but that's at 150 per hour

That's cool and all, but what happens if a lot of people use it and you go over your API request rate (on twitter)

So this is what your "A" in a shredder was for! Nice work, as always

That's an awesome icon!

I personally like it. It lets us know that that url that is being returned is, in fact, the url. It'll allow you guys to possibly change it later on (for some unknown reason) and know that if the programmer wrote their app well it wouldn't break.

because your question doesn't make sense. If I want to get badge data, I would want it to be in a spot where I can easily find it in the documentation. Maybe if there was one or two types of badges then your question would be valid, but with three it makes more sense to display it as a nested structure. That way, when I'm trying to find all badge data, I know that it's all contained within badge_counts and that that'll be the only place badge data is in.

Not trying to be mean, but can I downvote this twice?