Yes, we have a couple places in our code where we're forced to drop
protected users/statuses out of responses at the last minute, creating
inconsistent pagination rules. It sucks, and we're working on it.
On Thu, Oct 23, 2008 at 1:11 PM, GuyHagen <[EMAIL PROTECTED]> wrote:
>
> Does anybody else get this? I presume it's because some followers
> have their statuses protected, but I'd like a confirmation.
>
> The following is a brief list of counts of users showing up in
> subsequent page requests on a twitterer using statuses/followers. As
> you can see, the numbers occasionally drop below 100.
>
> ?page= : number of returned followers ("<user></user>")
> 990: 100
> 991: 100
> 992: 100
> 993: 100
> 994: 100
> 995: 100
> 996: 100
> 997: 100
> 998: 100
> 999: 100
> 1000: 100
> 1001: 100
> 1002: 100
> 1003: 100
> 1004: 99
> 1005: 100
> 1006: 100
> 1007: 100
> 1008: 100
> 1009: 99
> 1010: 99
> 1011: 97
> 1012: 100
> 1013: 98
> 1014: 91
> 1015: 98
> 1016: 97
> 1017: 98
> 1018: 100
> 1019: 96
> 1020: 96
> 1021: 97
> 1022: 97
> 1023: 97
> 1024: 97
> 1025: 97
> 1026: 100
> 1027: 96
> 1028: 98
> 1029: 98
> 1030: 98
> 1031: 100
> 1032: 97
> 1033: 99
> 1034: 99
> 1035: 99
> 1036: 99
> 1037: 96
> 1038: 98
> 1039: 99
> 1040: 98
>
--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
