Description: ------------ Twitter is switching to a new ID scheme for Tweets that will use unsigned 64-bit integers. PHP (and many other languages) do not have support for unsigned 64-bit integers. In order to circumvent this issue, Twitter is going to start providing both an "id" and "id_str" in their JSON/XML responses. Info: http://groups.google.com/group/twitter-development- talk/browse_thread/thread/6a16efa375532182 Example: {"id": 10765432100123456789, "id_str": "10765432100123456789"} In PHP, we're going to have to use id_str, because the id integer overflows. Personally, I'd prefer if this change was handled seamlessly within Services_Twitter. In other words, if I access $tweet->id, it should really return id_str, since $tweet->id will always be invalid when accessed within PHP. Additionally, any API functions that take a tweet id as a parameter will have to be updated to accept a string for the tweet id. I can help with a patch but I wanted to post here first. Thoughts?