Neither the 'before' case nor the 'now' case is correct. You'll only receive the 400 if none of the users specified have authorized your application. You'll receive a friends list for each user who has authorized your application. You can tell those who haven't by the absence of the friends list.
-John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Feb 15, 2011 at 11:52 AM, A.A.Novikov <al.an.novi...@gmail.com>wrote: > Hi, a couple of days ago I've noticed that the implementation of a > undocumented edge case changed: > > Let's say there are users A,B,C; users A & B have authorized our > twitter app, user C either hadn't or removed authorization shortly > after. > > BEFORE if used to return an HTTP 400 (or 401) when ANY of the A,B,C > hadn't authorized the twitter app > > NOW, if there's at least 1 user who has authorized the service, the > sitestream api returns 200, and simply does not pass any messages > about the users who didn't authorize twitter app. > > Which leads to an issue that currently the users of the sitestream > can't know for which subset of requested follow set of users it was > actually valid & successful. > > Would it be possible to simply respond with a JSON one-liner > immediately, reporting users with mismatched authorization? > > -- > 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 > -- 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