[twitter-dev] Change in API statuses/followers.json or bug?

[janole]

Hi,

my Twitter client is acting weird at the moment. One reason seems to
be a changed(?) reply format for the statuses/followers.json call.

A followers' status, which is a reply, is returned as:

status:{
in_reply_to_user_id:12345,
in_reply_to_status_id:
{in_reply_to_user_id:null,source:...,...}
...}

Wasn't the in_reply_to_status_id a int64 before? Now it's returned
as an object.

Ole @ mobileways.de

[twitter-dev] Change in API

[Sean Fawcett]

Hi:

A couple of months ago, I received an email from Twitter about some
changes in the API.  I was, at that time, up to my eyeballs with a
time sensitive project and did not have time to follow up.

Now, I notice that a very simple function that I created, allowing a
user to fill in a text field from a web page and post a Tweet, no
longer works.

Is there something I missed?  What do I need to do to make sure my old
code (March '09) now works with the API changes.

Any insight would be very helpful.
Thanks

Sean