Hey Aaaron,

When I call this Tweet the values are correct. Can you paste the entire
Tweet object as you receive it, and confirm your code isn't processing the
integer before displaying it to you.

twurl
/1/statuses/show.json?id=28480100643110912\&include_entities=1\&trim_user=1
{
  "coordinates": null,
  "created_at": "Fri Jan 21 15:52:39 +0000 2011",
  "favorited": false,
  "truncated": false,
  "id_str": "28480100643110912",
  "in_reply_to_user_id_str": "774675",
  "entities": {
    "urls": [

    ],
    "hashtags": [
      {
        "text": "hilowf",
        "indices": [
          100,
          107
        ]
      }
    ],
    "user_mentions": [
      {
        "name": "Steve Garfield",
        "id_str": "774675",
        "id": 774675,
        "indices": [
          0,
          14
        ],
        "screen_name": "stevegarfield"
      }
    ]
  },
  "text": "@stevegarfield sure. Def answr the questions now but go dir 2 the
community same time - tell & show #hilowf",
  "annotations": null,
  "contributors": null,
  "id": 28480100643110912,
  "retweet_count": 0,
  "in_reply_to_status_id_str": "28478713205096449",
  "geo": null,
  "retweeted": false,
  "in_reply_to_user_id": 774675,
  "user": {
    "id_str": "15010685",
    "id": 15010685
  },
  "in_reply_to_screen_name": "stevegarfield",
  "source": "<a href=\"http://www.tweetdeck.com\";
rel=\"nofollow\">TweetDeck</a>",
  "place": null,
  "in_reply_to_status_id": 28478713205096449
}

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Fri, Jan 21, 2011 at 9:08 AM, Aaron <wyrmw...@gmail.com> wrote:

> I am seeing this well w/ JSON. In fact, it's not just the
> in_reply_to_status_id_str, but also id & id_str don't agree!
>
> Example tweet: 28480100643110912
>
> Would love to talk to the twitter team to help solve this as it's a
> doozy for my particular app
>
> - Aaron
>  @aaronwhite
>
> On Dec 1 2010, 3:36 am, Matt Harris <thematthar...@twitter.com> wrote:
> > This is unexpected. Can you provide us with some sample Tweet IDs where
> > those fields are different so we can investigate further.
> >
> > Best,
> > @themattharris
> > Developer Advocate, Twitterhttp://twitter.com/themattharris
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Dec 1, 2010 at 12:18 AM, shunjie <shin...@gmail.com> wrote:
> > > Hi guys,
> >
> > > I saw that sometimes in_reply_to_status_id  is different from
> > > in_reply_to_status_id_str in JSON returned. This only happens recently
> > > (should be after the 53bit roll out).
> >
> > > Do anyone else encounter the 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
>

-- 
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

Reply via email to