PPL

Twitter sync should respect API rate limit.

Bug #688326 reported by Brad Phillips on 2010-12-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PPL
Medium
Christopher Adams

Bug Description

One option is to load contacts via statuses/friends and then load the rest as a background process.

yes, agree. we don't want to be offenders.

On Thu, Dec 9, 2010 at 3:00 PM, Brad Phillips <email address hidden>wrote:

> Public bug reported:
>
> One option is to load contacts via statuses/friends and then load the
> rest as a background process.
>
> ** Affects: ppl
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of PPL
> Developers, which is subscribed to PPL.
> https://bugs.launchpad.net/bugs/688326
>
> Title:
> Twitter sync should respect API rate limit.
>

--
Jon Phillips
http://rejon.org/
http://fabricatorz.com/
chat/skype: kidproto | irc: rejon
+1.415.830.3884 (sf/global)
+86.187.1003.9974 (china)

+65.8330.5807 (singapore)

I already re-engineered the Twitter contact import to require fewer API calls:

+1 call to get the user's avatar
+1 call per 100 friends

We're only likely to hit the API limit if the user has an enormous friend list. Still, the checks can be done:

$limit = $twitter->accountRateLimitStatus();
$remaining = $limit['remaining_hits'];

$limit = $twitter->accountRateLimitStatus();
$remaining = $limit['remaining_hits'];

Changed in ppl:
assignee: nobody → Christopher Adams (christopheradams)
importance: Undecided → Medium
status: New → In Progress

This should be pushed back until background sync processes are working, so that the system has a chance to "try again later" if the API limit has been reached.

Changed in ppl:
milestone: 0.2 → 0.3
Changed in ppl:
milestone: 0.3 → 0.4
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers