> > Also - if the embedded user object is supposed to be constant across all > the returned tweets, could it be "factored out" of the tweet array and only > transmitted once? You could send back the *whole* user object once and then > pages of arrays of tweets. You'd need to give the API call a new name, of > course, but it would be vastly more efficient.
we're investigating lots of different routes for this problem -- our goals are to remain backwards compatible, consistent, and simple. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
