Ok reading that does it mean each page view creates a call to Twitter and there is a potential limit of only 100 or so of these an hour?
The site I am using this on is likely to have visitor spikes of 100’s if not 1000’s as high visibility site – so if this is the case your otherwise excellent plug in would be unsuitable?
thanks
No, Twitter Widget Pro limits it’s calls to 20 per hour per config, where one config is a username and it’s settings. So if you have 4 widgets, one with user A showing retweets, one with user B showing retweets, one with user A not showing retweets, and another of user B again with retweets…you have 3 different configs. That would mean a max of 60 calls per hour to Twitter.
The problem is that the limits Twitter puts on unauthenticated requests are by IP, so if you have someone else on your same IP (at shared hosts there are often MANY other sites on your same IP), all their requests count against your limit. A single site that’s doing things wrong could use up the entire hourly limit for your IP in less than a second, and if they continue to do that, someone elses site could end up getting your IP further limited or even black listed by Twitter.
ok thanks for the clarification.
