On 9/8/10 7:15 PM, Julio Biason wrote:
> On Wed, Sep 8, 2010 at 1:54 PM, Tom van der Woerdt <i...@tvdw.eu> wrote:
>> The API doesn't check for blocked users. You need to implement that
>> manually.
> 
> So for every request for the user_timeline I need to request the list
> of blocked users, to have a proper list in case the user blocks
> someone in the website?
> 
> That sounds incredible stupid.
> 

I'm not 100% about my last post. Anyway, the documentation says this
about blocks :
> The block list should be cached locally - the change velocity is usually 
> quite low. If possible, save the cache to disk to avoid polling for the block 
> list upon startup. Timestamp the block list write time and only update 
> perhaps as infrequently as every 6 to 24 hours.

Tom

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to