Post edited 3:24 am – December 11, 2009 by kukhuvud

AaronCampbell said:

The solution for this is to increase the number of seconds to wait for a response from Twitter (default is 2). 

---

Where is this setting set?  I'm guessing it's a |twitter-widget| option, but I don't see it documented.

AaronCampbell said:

I'm not sure what you mean by having emptied your twitter inbox, but unfortunately getting the "Could not connect to Twitter" error could be a lot of things:

1. It could be a slow connection from your host to Twitter.  The solution for this is to increase the number of seconds to wait for a response from Twitter (default is 2).  Unfortunately, if you do this then if it's slow your page will load slowly too.
2. You could be bordering on your maximum number of requests per hour with Twitter.  If this is the case you'll need to cut back on access to the account through other methods.  The widget only uses 12 requests per hour, but if you also use something like tweetdeck, seesmic desktop, mobile twitter apps, etc they all use requests as well.
3. Twitter could be having problems.  You can't do anything about this, but it generally fixes itself if you just give it time.
4. There could be a routing problem between your server and Twitter (and not between you and Twitter).  Again, you can't do anything about this, but it resolves in time.

I love this widget, but it is not connecting nearly as much as it is disconnected.  I tried #1, up to 20 seconds, and #2 is not a factor, as I almost never check twitter.com, either with the iPhone or internet, unless the visitors to our site rack up "requests" whenever the page loads… Could that be the case?

Sometimes I get a connection, but mostly I do not.  Sure would like this to work better.

Blessings,

rcarbaugh