Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hi,
Just had a quick look at the twitter module and was unable to import any of my tweets.
Did a bit of digging and managed to pull up the error message, which was:
Rate limit exceeded. Clients may not make more than 100 requests per hour.
I definitely didn't make any more than 10 requests trying to figure out was wrong.
I also tried the URL that the module was hitting for the data directly in firefox and was able to retrieve the xml file fine.
I'm wondering if maybe twitter is seeing all users of the twitter module as one single client?
Cheers,
Deciphered.
Comments
Comment #1
pontus_nilssonI think I have the same problem. I have several twitter accounts on my site and I get 400 Bad Request. I run cron every second minute. Is there any setting for twitter how often it should connect to twitter? Any ideas how this could be solved?
Comment #2
elliotttf CreditAttribution: elliotttf commentedsubscribing. Same error here with two accounts and cron running every 15 minutes.
Comment #3
elliotttf CreditAttribution: elliotttf commentedComment #4
abraham CreditAttribution: abraham commentedTwitter has several forms of rate limiting. For their docs check out: http://apiwiki.twitter.com/Rate-limiting
The 2 basic forms are authenticated and unauthenticated.
Authenticated: Calls made using an account username and password. The rate limiting is global for that account so if you are using tweetdeck or tweetie calls from those accounts will count against the 100 calls/hour.
Unauthenticated: Calls that have no username/password associated with them. These are tracked by IP. If you are hosted on shared hosting other sites could be eating into the limit.
There are a number of tricks that could be employed in this module to use API calls more effectively but new issues should be opened for those.
Comment #5
Deciphered CreditAttribution: Deciphered commentedWhat you failed to take from this issue was that the error was a false negative, my 100 API calls had not run out, all my other clients (Tweetie, TweetDeck, etc) still had plenty calls remaining, yet the Twitter module fails every time on my online development site, hosted by Dreamhost.
It does, however, work when I use it on my XAMPP install.
Cheers,
Deciphered.
Comment #6
abraham CreditAttribution: abraham commentedDid you specify a password when you added the Twitter account to the Drupal profile? If not the import is done unauthenticated. Since it is Dreamhost the IP is probably shared with other websites that could be eating up the available API hits.
Try running both an unauthenticated and an authenticated rate_limit_status [1] from the server. (not from your computer)
[1] http://apiwiki.twitter.com/Twitter-REST-API-Method:-account rate_limit_status
Comment #7
geerlingguy CreditAttribution: geerlingguy commentedI can confirm that this fixed the problem for me (making sure I had a password). I originally had a password associated with the account, but I guess when I changed some other settings without re-entering the password on the twitter admin page, it didn't keep the password anymore.
Comment #8
Gilneas CreditAttribution: Gilneas commentedSame trouble here. When updating Twitter setup with a password for my account, the password is deleted right after clicking the save button.
Comment #9
abraham CreditAttribution: abraham commentedRate limiting is restricted by Twitter. There is nothing to be done with this module to alleviate the issue other then making sure accounts are authenticated.
Gilneas: Passwords are no longer supported by Twitter. Make sure you are using the OAuth version of this module.
Comment #10
Gilneas CreditAttribution: Gilneas commentedCan you explain that a little more detailed please?
I now installed Oauth module in version 6.x-2.02 in combination with twitter 6.x-3.0-beta3. But in twitter setup I cannot find instructions for Oauth. What's wrong?
Comment #11
abraham CreditAttribution: abraham commentedThis might help: http://drupal.org/node/649714
Comment #12
Gilneas CreditAttribution: Gilneas commentedYeah, right, this helps. Thanks a lot!