Why can't you just use
to get the lists the user is listed on...and just do a counter as you
go through them? It might require a few extra service calls, but at
the moment that seems like the most 'appropriate' way to determine how
many lists a given user is currently on.
On Tue, Feb 9, 2010 at 1:10 PM, Cameron Kaiser <spec...@floodgap.com> wrote:
>> Why would my IP get banned - the API allows developers to retrieve
>> almost every piece of data from user's twitter profiles so developers
>> don't need to scrape. I think if it's a closed site and they want to
>> protect content, then I can understand IP banning but if it's an open
>> system like Twitter, I don't see any reason why my IP would get
>> Maybe someone from the Twitter Platform team can chime in, especially
>> since I only scrape for list counts every 4-6 hours on a small set of
>> users for my application.
> That's probably why they haven't noticed you (yet). However, screen
> scraping gets around rate limiting and other controls Twitter places on
> the API. That's not exactly considered socially agreeable, and it's not
> fair on other API consumers. It's also against TOS.
> ------------------------------------ personal: http://www.cameronkaiser.com/
> Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
> -- It would have been funnier if I didn't have to think. -- Ashley Mills