Yes, you're right. My mistake. I had a browser plugin to format the JSON response, that's why it returned a wrong value.
Thanks. On Jan 24, 4:29 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Many JSON parsers/Javascript-like programming languages can no longer > consume our Tweet ID integers -- if you view the raw response of this API > request, you'll see the correct value for the ID integer -- but the act of > consuming the JSON by most processors will munge the integer. It's > recommended to use id_str instead. > > Taylor > > > > > > > > On Mon, Jan 24, 2011 at 6:01 AM, Edi <edi....@gmail.com> wrote: > > It seems the API returns a wrong id value for the original tweet in a > > retweet. > > > Take this as an example: > >https://api.twitter.com/1/statuses/show/29504582241484800.json > > > It returns: > > id: 29504533839216640 > > id_str: "29504533839216642" > > The id_str is the correct value. > > > Am I the only one having this issue? > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
