I think we can do a couple of things for you there. We’ll be changing our api throttling a bit to allow for better bursting behavior. Right now we are default to 1 request per second but we’ll be changing that to 60 requests per minute which should allow you to pull a good bit of information in bursts at one time.
The reason we don’t return time and move information in game lists (we don’t do it at /v1/games either) is that we have to fetch the information from the game state database (it’s not stored in our site relational database) so to do that for a full page of games at one time can add a lot of extra time to the api request which we would like to return as fast as possible. With the new bursting behavior you’ll be able to pull the games list and then go query those games without worrying too much about throttling unless your list is big.
We certainly understand what it’s like to have broken code out in production (we’re both professional software engineers and we’ve had it happen to us) no need to feel bad about it.
With a site this large there’s just no way for us to have perfect test coverage and when making huge changes like our 4.0 release bugs will inevitably creep in. I would point out that we put out a call for testers on our public beta site months before we released:
Having said that, we have (and will continue to) worked hard to fix those bugs. As mentioned in that post, this release provides us with a great foundation to continue building the site. We do rely heavily on our community to help us find problems and make suggestions on how things could run better… it’s just the nature of having a large project at this scale with a small team.