User revocation of an application is not a supported event.. You will find out when a user has revoked the application when you connect to Site Streams. Alternatively, if you haven't seen activity for a user for a while you could verify the tokens are still good by making a request to the verify_credentials REST API method using that users details.
More on verify credentials here: http://dev.twitter.com/doc/get/account/verify_credentials Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Feb 16, 2011 at 6:50 AM, A.A.Novikov <al.an.novi...@gmail.com>wrote: > Thank you for the timely reply, and it's actually what I meant when I > was describing the situation. > (And it used to be the case that request was refused if any of the > users didn't have authorization, I've been testing it, at least on > betastream.twitter.com 2-3 weeks ago) > > My point is that unless some sort of a timeout parameter is used there > is no guarantee for the application to know if some user in the stream > has invalidated the authorization. > > Right now I'm relying on an assertion that friend-list messages are > always clustered, i.e. once stream receives messages other than friend- > list no more friend-lists are received, but it's not convenient > because there's no telling how soon another message is going to > arrive. > > Can you give me some advice on how to solve this problem? > > > On Feb 16, 1:12 am, John Kalucki <j...@twitter.com> wrote: > > 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 Kaluckihttp://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 > -- 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