To be accurate: most ids do work... We had no httpstatus 500 errors for quite a while, so this is new and different and bad behavior. We've had a working application that has been functioning for more than a year, and way back when these errors were frequent, and then Twitter did alot of new/good work and they've all but gone away (at least on this api)... until now. .
On Jan 26, 12:39 pm, Kevin Marshall <falico...@gmail.com> wrote: > Yes - seems to be a problem for any id other than the example one in > the documentation: > > http://twitter.com/statuses/show/1472669360.xml(works) > > http://twitter.com/statuses/show/12735452.xml(reports no statuses, > but this is my account and so I can confirm that there are statuses > there to report -- ashttp://twitter.com/users/show.xml?id=12735452 > also confirms). > > BTW - if you use the user_timeline method, I think you can get the > same status stuff (http://twitter.com/statuses/user_timeline.xml?id=12735452) > > - Kevin > > On Tue, Jan 26, 2010 at 3:11 PM, Jeffrey Greenberg > > > > <jeffreygreenb...@gmail.com> wrote: > > For instance:http://twitter.com/statuses/show/15527375.xml > > > anyone else seeing these?