I'm trying to figure out the best way to do paging now that we have a maxID. Currently, on loading a page, I set the since ID to be the id of the first post returned from the api, and the max ID to the ID of the last ID returned from the api call plus 1. Now when I click next, I tell the API to get the posts with a maxID equal to my maxID and a count of twenty, and then reset the sinceID to the first post returned from that call, etc. That's working fi9ne, but something weird is going on when I attempt to go backwards. I would have thought that to go backwards, I would simply make a call to the getstatuses.json call with a since ID equal to the since ID I have saved and a count of twenty to get the previous twenty posts a user hasn't seen, but it seems to be taking me back to the beginning of the tweet stream. I'm looking at my code to see if there was a bug, but I wanted to check here to see if my algorithm made sense or if I was going insane.
