To collect all this info myself, I would need to operate some kind of service on an ongoing basis. This is not that practical with a pure client app like an iPhone app. Yes, I could build a server to collect all the info and what not, but it would be much more convenient if I could just go to Twitter site and look it up without having to build and operate something.
I do agree that it is probably not a big business problem for Twitter on a grand scale. But Twitter's success has largely come out of the ecosystem. It would be cool if Twitter invested in small things like this to keep us developers happy so that we could keep making money for both them and ourselves. J On Oct 9, 5:29 pm, nischalshetty <nischalshett...@gmail.com> wrote: > @Januus you could do that on your end as well, twitter doesn't > restrict you from keeping a count on the number of users of your app. > Nevertheless it would be awesome if twitter did it themselves, but as > we can see from the reply above by @taylor they have scaling issues > with the count and as far as I can tell, this would be low on their > priority (any company would keep this on low priority when they have > bigger problems out there to solve) > > -Nischal > > On Oct 9, 6:48 am, Jaanus <jaa...@gmail.com> wrote: > > > > > Twitter has been advertising better analytics for themselves about > > users, apps, and developers, as one of the key benefits of migration > > to OAuth. I believe its completely true, and it would be nice if you > > reflected a bit of that benefit back to developers in the form of > > "unique userIDs that have got a token for this consumer_key" like it > > used to be on Twitter site. Even if it were with a day's lag or such, > > it would still be valuable to developers, it does not have to be > > realtime and with a load impact at all. > > > J > > > On Sep 29, 7:55 am, Taylor Singletary <taylorsinglet...@twitter.com> > > wrote: > > > > The loading of the information would not scale for many clients, > > > resulting in whales when trying to load your application (lame but > > > true). It's best to track such information by your own means. I'd be > > > happy to look up the value for you if you follow up with me off-list. > > > > Thanks, > > > Taylor > > > > On Wed, Sep 29, 2010 at 7:51 AM, Duane Roelands > > > > <duane.roela...@gmail.com> wrote: > > > > I used to be able to go tohttp://twitter.com/oauth_clientsandsee > > > > how many users have authorized my application. Twitter appears to > > > > have removed those numbers. > > > > > Where can I go to find out how many people have authorized my > > > > application? > > > > Why was this information removed? > > > > > -- > > > > 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