On Jun 27, 9:55 pm, Nick Arnett <[email protected]> wrote: > There are parameters available to avoid the ambiguity. > See http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_t...
Yes, I know, that's what I am now using. I was just wondering why there should be such an ambiguity in the api. > > Nick > > On Sat, Jun 27, 2009 at 7:52 AM, X10 <[email protected]> wrote: > > > When retrieving statuses with /statuses/user_timeline/1250.xml there's > > an ambiguity. Should Twitter return the tweets for userid=1250 or for > > screenname=1250? Matter of fact, if you use this url for retrieving > > tweets by screen name, you'r ok unless a user has a numeric screen > > name, in which case you get the tweets of another user who happens to > > have that particular user id. > > It's an interesting way of getting to know other Twitter users, but > > I'm not sure it is desired behavior of the system.
