Thanks for the help. I realize now that Klout actually does authenticate users when they sign up.
Will look into the stream API. Cheers. On Jul 20, 11:33 am, John Kalucki <j...@twitter.com> wrote: > The best way to do this is to take a higher level of Streaming API access, > then compute and persist the results on your end. For example, if you take a > feed of all Retweets, or the full Firehose, you can perform retweet > calculations for all public users. With track, you could track mentions of a > subset of users, or with the firehose, all public mentions of all users. > > -John Kaluckihttp://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > > > On Tue, Jul 20, 2010 at 8:15 AM, Sachin <sachinmo...@gmail.com> wrote: > > Using the GET statuses/mentions request I can return all the @mentions > > and RT's for the authenticating user. The API documentation says that > > no authentication is required, but since there is no user ID parameter > > I can see that it does in fact require authentication (reading the > > forums have confirmed this I think). > > > Does anyone know of a way to get the # of mentions and RTs for a user > > ID within a timeframe (i.e. last 30 days)? > > > Using the Search API I can get some results in json... but it seems to > > be only returning the last 8 or so mentions. > > > Does anyone know how applications like Klout are getting these stats? > > (http://klout.com/uschles/scoreshows 267 mentions and 63 retweets). > > I'm sure they are still only accurate within a certain timeframe but > > I'm curious as to how they're getting these stats at all without > > authentication from the user. > > > Any help would be much appreciated. > > > Thanks, > > > Sachin
