Taylor, I found one other in my debug logs: 20486403894, also from twitterapi. None others yet. Hope this helps you.
Mark On Aug 9, 9:29 am, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Hi Mark, > > We're looking into this and are not quite sure what's going on with these > particular statuses. If you come across any other status ids that can't be > fetched via statuses/show, cannot be favorited, or retweeted (all three > actions fail with these particular tweets), please let us know the status id > so we're aware. > > Thanks, > Taylor > > On Mon, Aug 9, 2010 at 3:48 AM, Mark Krieger <markskrie...@gmail.com> wrote: > > I tried to 'favorite' an update by twitterapi over the weekend in > > twitter, nothing happened, so I tried to read that update in my own > > application -- and I then tried to read a few other updates from > > twitterapi. I get back a statuses list in home timeline, then I try to > > read more information about the updates in question, and I always get > > an error. I think twitter must also get an error, since those updates > > seem to be unavailable there too. Here is what I see in my debug > > output for one of these updates, any ideas? > > > {"request":"/1/statuses/show/20499308096.json","error":"No status > > found with that ID."} > > > I get the ID from the updates listed in a getstatusesHometimeline. I > > would suspect my application, but it does this for everything else > > fine, and only a subset of updates/statuses from twitterapi seem to be > > failing, and twitter itself is failing to allow a favorite (for > > instance) on these. Are these just 'lost' statuses/updates which I > > should not worry about? > > > thanks, > > > Mark