Loading Profile...
Twitter Rate Limit
Is anybody else experiencing Twitter "exceeded 70 requests per hour" error messages in Twitterrific (or any other client, for that matter) since using SocialThing?
I've had the problem consistently since I put my info into ST. I just changed my Twitter password to see if that isolates the problem.
I've had the problem consistently since I put my info into ST. I just changed my Twitter password to see if that isolates the problem.
7
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solution from the company
-
According to http://groups.google.com/group/twitte... which is twitter's API Documentation, there is a hard rate-limit of 70 requests per hour per user. That is to be read: "regardless of which twitter api client you use, you get 70 total requests per hour". Now if you are using twitterific at it's highest frequency, you "use up" 60 requests in one hour, leaving only 10 for any other client you use.
Obviously, twitterific's usage goes down if you have it auto-refresh less frequently than every 3 minutes.
On the other hand, if you refresh your Lifestream on socialthing, at it's maximum frequency(currently 5 mins), you only use 24 of your twitter rate limit every hour.
We've thought about this considerably, and therefore attempt to use as few of your updates as possible, and are actively working with twitter on XMPP technology in order to receive near-realtime updates (stay tuned).
I hope this provides some explanation as to why it might -appear- that we are breaking your twitter.
The company and 2 other people say
this solves the problem
The best solutions from everyone
-
DOH! I meant the API Twitter account at http://twitter.com/api_updates/status...
The company says
this solves the problem
-
According to Alex Payne (API dev at Twitter.com) they had changed the rate limiting for MacWorld. Of course their servers got tremendously overloaded and such so it was causing a few problems. Things should be back to normal with Twitter by now.
You can read a quick blurb on the twitter blog at http:/blog.socialthing.com
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?So, after I changed my password the rate limit error went away. I'll keep monitoring it to see if it comes back. -
Inappropriate?Nevermind...got the error again, so I am pretty sure that it's a problem on Twitter's end. I read somewhere that they changed the rate limit for MacWorld, and that the change might still be in effect.
-
Inappropriate?Definitely having same issue with other Twitter clients...I'm blaming Twitter API fallout from yesterday -
Inappropriate?According to Alex Payne (API dev at Twitter.com) they had changed the rate limiting for MacWorld. Of course their servers got tremendously overloaded and such so it was causing a few problems. Things should be back to normal with Twitter by now.
You can read a quick blurb on the twitter blog at http:/blog.socialthing.com
The company says
this solves the problem
-
Inappropriate?DOH! I meant the API Twitter account at http://twitter.com/api_updates/status...
The company says
this solves the problem
-
Inappropriate?This is happening again, multiple errors a day with very minimal activity.
I’m frustrated
-
Inappropriate?if you are logging into twitter from multiple places it depletes your hourly allotments. we have this issue from twitbin users. only solution is to update less frequently. -
-
Inappropriate?According to http://groups.google.com/group/twitte... which is twitter's API Documentation, there is a hard rate-limit of 70 requests per hour per user. That is to be read: "regardless of which twitter api client you use, you get 70 total requests per hour". Now if you are using twitterific at it's highest frequency, you "use up" 60 requests in one hour, leaving only 10 for any other client you use.
Obviously, twitterific's usage goes down if you have it auto-refresh less frequently than every 3 minutes.
On the other hand, if you refresh your Lifestream on socialthing, at it's maximum frequency(currently 5 mins), you only use 24 of your twitter rate limit every hour.
We've thought about this considerably, and therefore attempt to use as few of your updates as possible, and are actively working with twitter on XMPP technology in order to receive near-realtime updates (stay tuned).
I hope this provides some explanation as to why it might -appear- that we are breaking your twitter.
The company and 2 other people say
this solves the problem
-
Inappropriate?Keep in mind that Twitter hasn't been very stable in recent weeks. I've seen this detrimentally affect applications using the API...so if Ben's very well written explanation of the rate limiting still doesn't seem to explain your problem it may have nothing to do with Socialthing and more to do with Twitter.
-
Inappropriate?So, this means that if I use Twitterfox to see what my Twitter updates are, and publish my Twitters on my log, I exceed 70 requests to twitter an hour? How's that possible?? It's not as if I am constantly hitting the refresh button or anything :(
I’m annoyed
-
Inappropriate?i'm getting the same error with twitteriffic on mac and Spaz on pc. I don't run them at the same time, even changed my password to be sure. I'm also not using any other apps/sites like SocialThing.1 Comment Add a comment
This solves the problem
-
we've got an update coming very soon that solves this issue, almost altogether. hope that helps! -
Inappropriate?this stuff ain't hard guys. an API is sometimes overkill ya knows
my $cmd = "curl -s -I http://twitter.com/";
my $url_header = `$cmd`;
if ($url_header =~ /200 OK/){
my $valid_string = "xml";
my $cmd = 'curl -u -s ' . $username . ":" . $password .' -d status="' . $msg . '" ' . "http://twitter.com/statuses/update.xml";
my $result = `$cmd`;
if ($result =~ /$valid_string/){
print "status updated yo";
}
else{
print "invalid response \n";
}
}
else{
print "twitter down!";
}
I’m frustrated
EMPLOYEE
