I'm using your package on a few production websites, now i wanted to add it to another website and quickly found this error:
<hash><error>Rate limit exceeded. Clients may not make more than 150 requests per hour.</error><request>/1/statuses/user_timeline.xml?screen_name=rikhelsen</request></hash>
it appears tha API won't allow that many requests for unauthorised users..
Hi Rik, Well this could be a number of things, if the user account is being checked often on say tweetdeck or a mobile phone along with the site this could all contribute to the problem.
What I could suggest is caching the macro perhaps to say 15 to 20mins if your site has a large amount of traffic that you think could be contributing to this rate limit.
is there any way to make the package use the authenticated API ? (or cache the xml feed for 3 hours?)
There's 20 people here using the same outbound ip, using tweedeck and mobiles using tweetdeck etc. then we also have 3 IIS servers sharing the same outbound ip where we have websites using the api to display tweets...
right now all of them are broken because of the number of api calls... i'm still thinking about different ways to fix this. It appears i can request an increase in the call-limit, i hope they respond fast :/
Hi Rik, I haven't looked at any of my packages for a long time, just because of limited free time with new job at the HQ and planning for a wedding. You could modify the XSLT to use the GetXML call where you can set the cache time, or alternatively cache the macro itself.
The code is open source and your more than welcome to work on it if you want to add authentication to it.
Rate limit exceeded. Clients may not make more than 150 requests per hour.
I'm using your package on a few production websites, now i wanted to add it to another website and quickly found this error:
it appears tha API won't allow that many requests for unauthorised users..
Anyone else encountered & fixed this?
Hi Rik,
Well this could be a number of things, if the user account is being checked often on say tweetdeck or a mobile phone along with the site this could all contribute to the problem.
What I could suggest is caching the macro perhaps to say 15 to 20mins if your site has a large amount of traffic that you think could be contributing to this rate limit.
Thanks,
Warren
is there any way to make the package use the authenticated API ? (or cache the xml feed for 3 hours?)
There's 20 people here using the same outbound ip, using tweedeck and mobiles using tweetdeck etc. then we also have 3 IIS servers sharing the same outbound ip where we have websites using the api to display tweets...
right now all of them are broken because of the number of api calls... i'm still thinking about different ways to fix this. It appears i can request an increase in the call-limit, i hope they respond fast :/
Hi Rik,
I haven't looked at any of my packages for a long time, just because of limited free time with new job at the HQ and planning for a wedding.
You could modify the XSLT to use the GetXML call where you can set the cache time, or alternatively cache the macro itself.
The code is open source and your more than welcome to work on it if you want to add authentication to it.
Cheers,
Warren
is working on a reply...