Well, it turned out to be one of those micro mistakes. I was reading the lasttweetid from a file by <code> lastid = open('lasttweetid').read </code> which was appending an "\n" at the end thus messing with the request generation in accessToken. So, just need to make it <code> lastid = open('lasttweetid').read.strip </code> and everything is fine. Now that my pet projects are OAuth-enabled, I can heave a sigh of relief!
- [twitter-dev] OAuth throws HTTPBadResponse error when used to ... kanny
- [twitter-dev] Re: OAuth throws HTTPBadResponse error when... kanny