Yes, you need an account with Twitter to use this plugin.
A Cli.gs account is entirely optional. Without an API from Cli.gs, a "public" Clig will be generated. The redirect will work just fine, but you won't be able to access statistics on your Clig. Bit.ly does require an API key and username, however. Regardless, you don't need to have an account with either service to make effective use of the WP to Twitter plugin.
If Twitter isn't available, you'll get a message telling you that there's been an error with your Twitter status update. The Tweet you were going to send will be saved in your post meta fields, so you can grab it and post it manually if you wish.
If your URL shortening service isn't available, your tweet will be sent using it's normal post permalink. You'll also get an error message letting you know that there was a problem contacting Cli.gs or Bit.ly.
Twitter.com allows API applications to register themselves with the service, so they can provide information about the source of your Tweet. WP to Twitter is a registered user agent with Twitter.com. The same effect is seen if you use any other registered Twitter client.
Well, there isn't much I can do about that - but the plugin will check and see whether or not the needed methods work. If they don't, you will find a warning message on your settings page.
No. They're private.
There was once an unresolved bug which effected some servers causing the WP-to-Twitter settings page to fail. I haven't heard a report of this problem for quite a while, so I believe it's gone, but if it does show up again, you can get around the problem by commenting out approximately lines 191 - 256 in wp-to-twitter/wp-to-twitter-manager.php. (Version 1.4.0.) . (These numbers change from version to version, but there are comments in the code to help you out.)
Only posts which you scheduled or edited after installing the plugin will be Tweeted. Any future posts written before installing the plugin will be ignored by WP to Twitter.




