Hi, *I have oauth codes that are currently working very well with the public sample stream. However, when I try to reuse those codes for site stream, I hit 401 error all the time. Can anyone please kindly brief the difference of oauth authentication between sample stream and site stream? * >A little bit detailed info regarding what I am doing: >For site stream, I am using app X's consumer key/secret, and its own access token/secret. >I set "follow" to User Y's id who has authorized app X with read/wirte access. >Like the smaple stream, I am posting to sitestream.twitter.com/2b/site.json.
>However, no luck with 401 in return. *ON THE OTHER HAND, I tried with GET method using the sample test code of sitebucket project. It sends the following but 401 in return as well.* >The keys/secrets are the same as those I used for the POST attempt. >GET https://sitestream.twitter.com/2b/site.json?oauth_body_hash=2jmj7l5rSw0yVb%2FvlWAYkK%2FYBwk%3D&oauth_nonce=96753402&oauth_timestamp=1305161637&oauth_consumer_key=gXXXXXXXXXXXXXXgnDQ&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_token=22222222-mobcMMMMMMMMMMMMMMMMMMMYbjZ&follow=299999991&oauth_signature=VbFuMVDK39PbpaoYF2HxA7U14dU%3D&with=userHTTP/1.1\r\nHost: sitestream.twitter.com\r\nAccept-Encoding: identity\r\n\r\n *So whether I should use GET or POST, and what is going wrong in my codes or the sitebucket?* Thanks, michael -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
