Hey there, I've had a site up and running for quite some time now (July 2010) since Dec 14, and a little after 2:30 (Mountain) we stopped receiving tweets from that service call. After checking in on it today I discovered I was receiving a 401: Incorrect signature error.
Here is my request /1/mdcpartnerssite/lists/executives/statuses.json? oauth_consumer_key=KQSwCfwSi2QEW9l6Yu8bg&oauth_nonce=caf8db043f02f2612675cfc2b64755c1&oauth_signature=hA6%2FA0VtOSyFAxk3Qa4InU %2FrAdo%3D&oauth_signature_method=HMAC- SHA1&oauth_timestamp=1292540218&oauth_token=154351009-8yk6Cl0bqA9VzomDPrFsS2JmfnGgox1UHo6eZAOd&oauth_version=1.0&page=1&per_page=200&since_id=9996331253 Here is my base string GET&http%3A%2F%2Fapi.twitter.com%2F%2F1%2Fmdcpartnerssite%2Flists %2Fexecutives%2Fstatuses.json&oauth_consumer_key %3DKQSwCfwSi2QEW9l6Yu8bg%26oauth_nonce %3Dcaf8db043f02f2612675cfc2b64755c1%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1292540218%26oauth_token %3D154351009-8yk6Cl0bqA9VzomDPrFsS2JmfnGgox1UHo6eZAOd%26oauth_version %3D1.0%26page%3D1%26per_page%3D200%26since_id%3D9996331253 Please let me know if there is any other information you need that would help in this manner. Did something change on twitter's end that required some more strict checking, that I might not be adhering to? I've also noticed a few other's mailing in about 401 issues. Any help would be greatly appreciated. Thank you! Brian Wigginton Interactive Developer Crispin Porter + Bogusky -- 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: http://groups.google.com/group/twitter-development-talk