I'm no longer seeing the updateTweetCount error when rendering the iframe directly, so this looks like the best method to allow AJAX updates.
An additional advantage is that you can make the iframe slightly bigger than that generated by the Twitter JS, eliminating clickjacking warnings from the NoScript Firefox plugin. -- 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