The blocks/blocking method appears to be similar to the statuses/ friends and statuses/followers methods, but I believe the documentation is incomplete for all three.
According to the API spec, each call to statuses/friends and statuses/ followers returns a "page" of up to 100 users (and their most recent statuses). Pages will contain less than 100 statuses if either a suspended user is (not) present in the page, or the page is the last page. A maximum of 3200 users / statuses can be retrieved. Thus the maximum value of the page parameter would appear to be 32. However, as suspended users are elided from the returned information, if the user has 3200 friends / followers or more, is it then possible that it would take more than 32 pages to get the 3200? If so, how does one easily and reliably determine that a page is the last page? Do you just keep asking for the next page until, e.g., you get a page with 0 users and then you've gone one too far? Or is the 3200 maximum reduced by the number of suspended users? Again according to the API spec, each call to blocks/blocking returns up to 20 users (and their most recent statuses), and the method supports a page parameter. Are suspended users elided from the returned information, as with the statuses/friends and statuses/followers methods? Is there a maximum of 3200 users / statuses? Is the maximum value of the page parameter then 160? And again, how can one easily and reliably determine that a page is the last page? BTW, with a page size of 20 and a maximum of 3200, a user with a lot of blocked users may easily exceed the rate limit of 150 requests per hour, even with only one attempt to get all the blocked users. Is it possible to get the maximum page size increased to 200, both for consistency and to avoid a possible rate limit? I may be wrong, but I think it's unlikely a user would have 3200 blocked users, at least with the current usage of blocking. But I need the answers to these questions so I can effectively program the use of these methods. I hope I can get definitive answers from twitter on this (And maybe an update to the documentation?), but any insight from anyone on this will be greatly appreciated. Thanks in advance, Jim Renkel
