http://code.google.com/p/twitter-api/issues/detail?id=214
On Sat, Mar 14, 2009 at 22:52, disturb...@googlemail.com < disturb...@googlemail.com> wrote: > > An issue has recently come to my attention which I'd like to ask > about; it's not answered in the FAQs or anything so this seems like > the best place to ask. > > Basically, the search API returns a 'from_user_id' for each result > which one would expect would correspond to each user's 'id' attribute > as returned by the twitter API (see > http://twitter.com/users/show/user_id.json > as an example which returns this 'id' attribute). However, a user's > Search API ID and their Twitter API ID are completely different from > one another. It seems the Search stores users in a different database, > or under a different primary key, etc., and this has been a little > confusing for me as I thought it was an issue in my own application. > > I just want to know if this is a (known or unknown) bug, if it will be > remedied in the upcoming changes to the Search API, and if there is a > simple method/algorithm to obtain a user's Twitter ID from their > Search ID. > > Regards, > Zack > -- Abraham Williams | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from: Madison WI United States.
