Hi Doug, And thank you for your answer !
I hope you'll be able to fix it soon (for the time being, I'm retrieving the right ID from the the Rest API, which makes the process a little longer). Could you tell me if I can trust this field as a simple "reply" flag (even if it's not the correct ID) ? I mean : - If "to_user_id" is not NULL, it means the tweet is a reply to another tweet. - If "to_user_id" is NULL, the tweet is not a reply. Take care, Arnaud. On Mar 10, 6:54 pm, Doug Williams <[email protected]> wrote: > Looks like you have stumbled upon issue > 214,http://code.google.com/p/twitter-api/issues/detail?id=214 > > If you need help with a workaround, please let me know. > > Cheers, > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Tue, Mar 10, 2009 at 1:37 PM, twitoaster > > <[email protected]> wrote: > > > Hello ! > > > I have been working on the Search API, and I noticed the "to_user_id" > > field retrieved (you only have it using json method) doesn't seem to > > be correct. > > > For example, with a search on "to:mashable" : > > - "to_user" retrieved : mashable (correct) > > - "to_user_id" retrieved : 10385 != 972651 (incorrect) > > > What is this int for ? Did I miss something ? > > > All the best, > > Arnaud.
