I am also having the same problem with "not found" errors.  I've found
I can sometimes get a response if I use the old format of /statuses/
show.json?id=xxxx, but this doesn't work consistently.  Could it be

Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to