Have there been any updates regarding this subject?

Kind regards,
Arno / @itavero

On 9 aug, 16:06, Taylor Singletary <taylorsinglet...@twitter.com>
> We'll have a solution for this announced soon that will allow you to move
> more seamlessly between the (non-OAuth 1.0a) access tokens that make up
> @Anywhere requests and server-side REST requests using OAuth 1.0a access
> tokens.
> There are also other things you can do with @Anywhere using advanced
> portions of the @Anywhere API -- including, for instance, retrieving a list
> of the user's follower IDs. You can read a bit about this 
> here:http://groups.google.com/group/twitter-dev-anywhere/browse_thread/thr...
> Taylor
> On Sat, Aug 7, 2010 at 12:25 AM, knc <kishor...@gmail.com> wrote:
> > Hi, I am a little confused here. I am using @anywhere's (with the JS
> > file include) to authenticate a user into my application. After this,
> > let's say I would like to retrieve a list of the user's follower IDs -
> > how do I do that? I'm guessing I need to use the REST API for this,
> > but since the user is already authenticated, how will the new flow be?
> > How do I get the Oauth token and secret to make the calls with?

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: 

Reply via email to