You're not the first to report this issue, I'm afraid. This crops up from time to time due to some low-level, complicated caching logic in our system. We're constantly ironing out this code, but I'll double-check the update method and see if there's any glaring issues there.
On Thu, Dec 11, 2008 at 10:05, Lee Semel <[email protected]> wrote: > > Just to clarify, here is an example of the request we are sending and > the json that's returned: > > REQUEST > http://twitter.com/statuses/update.json?status=%40sixuntilme%2C+you+were+nominated+by+%40jakerutter+for+a+%23personal+Shorty+Award+http%3A%2F%2Fbit.ly%2FLAIv > > STATUS CODE > 200 > > RETURNED > data={"in_reply_to_user_id":11676742,"truncated":false,"text":"@HughBriss, > you were nominated by @AgingBackwards (and 5 others) for a #design > Shorty Award http:\/\/bit.ly\/SMcZ","user":{"description":"The best > short content creators on twitter in > 2008","url":"http:\/\/shortyawards.com","name":"Shorty > Awards","protected":false,"profile_image_url":"http:\/\/s3.amazonaws.com\/twitter_production\/profile_images\/66792558\/logo_normal.png","screen_name":"shortyawards","followers_count":750,"location":"","id":17663756},"in_reply_to_screen_name":"HughBriss","favorited":false,"created_at":"Thu > Dec 11 16:20:11 +0000 > 2008","in_reply_to_status_id":1051493141,"id":1051503605,"source":"web"} > > In the JSON, the 'text' field is a status from 2 hours ago. It > completely ignored the update. > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
