> Sorry, what hack is that? I've heard a bunch of advice on working > around this, but nothing conclusive.
I believe he means changing from https://api.twitter.com to http://api.twitter.com. I can confirm that this works for me as well. Obviously not ideal, but an interim solution? -- 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
