Socialite - twitter requests/refreshes needs to learn how to count
Ken
via web
With the latest two versions of Socialite that have the increased twitter refreshes of 350/hour, I changed my settings to refresh every minute. However, I find I hit the cap within 15-20 minutes, what gives?
As a result of this, I'm not particularly fond of the 1 minute to 5 minute refresh time increment, as I used to have it set at 2 minutes. A more customizable setting with more options would be nice in the next update, as well as fixing this counting issue so that I don't run out of refreshes so quickly.
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Adam on 12 Mar, 2010 11:45 AM
Getting this too, but only since today's (or late yesterday?) update. Facebook authentication fixed, Twitter broken. Please fix!
Support Staff 3 Posted by Luke Hefson on 12 Mar, 2010 12:12 PM
Hi gys,
Thanks for the message. I'm sorry to hear that you are having issues with Socialite, I understand what an inconvenience this may be for you.
@Ken - Unfortunately at this stage if you have a large number of lists the refresh limit may be hit quite quickly, so for the time being you may need to set your refresh to evey 5mins. However, Twitter are changing their limit to 15,000 in April so this should help resolve the issue.
@Adam - How exactly is the Twitter service broken for you? Have tried removing and re-adding the service?
Kind regards,
Luke
-- Luke Hefson
Support & QA, Realmac Software
Our support team are in the office between 9am and 5pm UK time, Monday to Friday, and we aim to answer all requests within one business day.
4 Posted by Adam on 12 Mar, 2010 12:17 PM
Hi Luke,
Thanks for the response. I haven't altered my Twitter settings in any way shape or form, just updated the software this morning, and I now get 'Limit 350 requests reached' message after about 40 minutes. It never did that before the latest update. I have one hash-tag search inside my Twitter section, that's the only thing that's different from the 'standard' set up when I add a Twitter account to the app. The refresh rate is set at 1 minute.
Haven't tried removing/adding the service yet, I'll try that now... Although why that would fix the issue is beyond me, it's clearly something to do with the update, not the service!
Cheers
Support Staff 5 Posted by Luke Hefson on 12 Mar, 2010 12:48 PM
Hi Adam,
Do you have many list in Twitter? Have you tried setting the refresh rate to 5 minutes?
Kind regards,
Luke
-- Luke Hefson
Support & QA, Realmac Software
Our support team are in the office between 9am and 5pm UK time, Monday to Friday, and we aim to answer all requests within one business day.
6 Posted by Adam on 12 Mar, 2010 01:01 PM
Hi Luke,
As I previously stated, my Twitter service is 'standard' with the exception of a hash-tag saved search. And I would like my refresh rate to remain at 1 minute, hence the issue.
Support Staff 7 Posted by Nik Fletcher on 12 Mar, 2010 02:06 PM
Hi Adam
In preparation for Twitter raising to 1,500 we've removed the rate limiting. As a result, a few folks may now use up API calls far quicker. In previous versions, we artificially limited the refreshes to minimise API usage, however as Twitter are gradually rolling out more API requests per hour, we've removed the artificial limiting on our end [such as lists being refreshed less regularly].
For now, the only way to work around this issue will be to not refresh every minute, however, Twitter have said that the API limit will be raised in the next few weeks [for their Chirp conference] so it shouldn't be too long before these refresh limits are no longer a problem.
Thanks!
Nik
8 Posted by Ken on 12 Mar, 2010 02:30 PM
Luke and Nik,
Thanks for the reply. It doesn't have anything to do with the lists, as I know Socialite refreshes every third time. As I've seen both of my twitter accounts (one following 40, the other less than 10) hit the cap nearly at the same time. One with 2 lists that are relatively small, and the other without any lists respectively. And both come rather close to reaching the cap at 5 minutes as well.
But even if you do the math, the lists should not result in the hitting of the cap within such a short time. So it sounds as if Socialite is making multiple API calls simultaneously or very quickly repeatedly possibly due to bad logic in a refresh loop or some other call/function. Because if this is the case, even when/if twitter increases the cap it just means that Socialite will have that many more to use, and not necessarily resolve the issue, and the cap could still be hit quickly.
I should note, that previously I could have twitter being refreshed every minute using previous versions (no significant changes in amount of people I followed), and make it through the hour without hitting the cap. However if I had a conversation via tweets I would hit the cap due to the additional requests, hence why I set it at 2 minutes.
Support Staff 9 Posted by Nik Fletcher on 12 Mar, 2010 04:53 PM
Hi Guys
The lists are now refreshed every refresh [we're getting things ready on our end for Twitter allowing 1500 requests per hour in the next few weeks]. We're continuing to look into this issue, however. The number of folks followed doesn't actually affect the API requests: it's more Profile peeks, searches and Lists that can hamper the requests.
Thanks!
Nik
Nik Fletcher closed this discussion on 18 Mar, 2010 10:24 AM.