Non-browser app 1.1

marcog612 · 2012-11-29T22:03:24.000Z

Hi, I developed a small app in VC++ that performs tag searches using search.twitter.com, such like “http://search.twitter.com/search.json?q=tester9000&rpp=10&result_type=recent&include_entities=1”. Will the API 1 shutdown in march/2013 affect me? I don’t need anything else than that. Never had to authenticate. I use it to create message interactive projected screens, just need the profile picture, comment, and image entity.

Thanks

marco.g

episod · 2012-11-30T16:34:59.000Z

Come March 2013, you’ll need to leverage OAuth to communicate with the Search API from your console application, likely through hard-coding an access token representing your identity and relationship with the application.

JohanOsVenter · 2012-12-04T06:44:00.000Z

So this is the recommended solution? Using ‘any’ token-secret for your application? I’m asking because our web-app is using search-API, and does not require a user to be logged in ( to Twitter or otherwise ) to see the results of this.

Is there an approximate timeline for ‘Application authentication’ as mentioned here https://dev.twitter.com/docs/auth/oauth ?

episod · 2012-12-04T15:28:23.000Z

There’s no timeline available for when app-only auth will be available but I wouldn’t rely on the rate limits for that scenario necessarily being enough for your user base. I would strongly recommend instead thinking about requiring Twitter login on your site when showing/retrieving Twitter data instead – it’s going to be the only way to reliably scale your usage of the API with your site growth.

JohanOsVenter · 2012-12-05T06:35:40.000Z

I see, I somehow thought the rate-limit was per application. Just read the documentation again, as you say it’s per-user-per-application. Will just swop out with the client’s token when I have one. Wish me luck breaking this to the boss (requiring twitter login to see tweets )