u. So you would start
>> paginating from the start and keep going until you reach a "known"
>> follower. At that point
>> you should have a list of all new followers. You would still need to scan
>> the entire follower list
>> to find unfollows (if you need tha
ever, if I were just fetching the latest follows, it seems like I
could
do this at a higher frequency and not affect twitter.
Questions:
1. Is there a better way to do what I want with existing API?
2. Are there emerging features that could make this better?
Thanks,
Zero
ys provide an API. If it
can't be changed, it could be solved with docs.
I'm not whining, I'm just sayin...
Zero
On Fri, Mar 12, 2010 at 1:24 PM, Mark McBride wrote:
> Am I missing something regarding the complexity of doing this?
>
> Ruby pseudo-code:
>
> my_unr
cent). It would be easy enough to
put another switch that gives you the
least recent, and default to most recent. That provides you will the result
you want (people automatically get
most recent), but allows anyone who needs the ability (most programmers), to
scan forward easily.
Respectfully,
count set to
however number of tweets you want to move forward by.
I'm somewhat surprised no one has commented on this design flaw (which
makes me suspicious, perhaps I missed something obvious). If so,
apologies.
Thanks,
Zero
