Makes sense to me, Jim, although it may have to wait until the next major release of the API. If you wouldn't mind, please open an issue for this enhancement at http://code.google.com/p/twitter-api/issues/entry
On Tue, Oct 14, 2008 at 5:37 PM, jim.renkel <[EMAIL PROTECTED]> wrote: > > When you request a list of a user's friends (ah, others being > followed, in the new terminology :-) ), you get back their latest > status updates, which is useful for many applications, including the > one I am developing. > > What my application REALLY needs is the last location update of each > of the users that are being followed. I can loop through the followed > users list, get their profile, and extract the location, but with even > a modest sized list you quickly hit the rate limit. > > To generalize this, I request that a user's location be returned > whenever any other information about that user is included in a > returned list. (If the returned information is specific to a single > user because the request was for information about that user only, > then I guess it would be OK to have to separately request the profile > for that user.) > > Comments are welcome, appreciated, and expected. > > Thanks in advance, > > Jim Renkel > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
