Twitter API 1 is now unavailable :(

[RobbyZ]

Been happily using this on my website for a while, but it now looks like Twitter no longer supports API 1:

{"errors": [{"message": "The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.", "code": 68}]}

Will API v1.1 be supported?

[ghost]

I didn't get the error message, but my twitter stream isn't working anymore either.
I've noticed a lot of sites do get that error when I searched for Twitterlib on Google though.

[Broeiend]

Yup, we need to build in a AUTH key now...:(

[remy]

I'm on holiday ATM - but I've got a fix in the works for when I return. So
hold tight, and please spread the word whilst I'm away.

Thanks.

On Friday, June 14, 2013, Broeiend wrote:

Yup, we need to build in a AUTH key now...:(

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-19461709
.

— Remy

[makkynz]

Hi Remy,

Any idea when you will have this fix ready?

[remy]

I spent today working on it but hit a blocker. Not sure where I go next for
now.
On 21 Jun 2013 18:57, "makkynz" [email protected] wrote:

Hi Remy,

Any idea when you will have this fix ready?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-19830964
.

[RobbyZ]

My understanding of the new Twitter API is that the client has to be
authenticated via OAUTH, which is problematic since no one should
distribute client secrets publicly.

It's a PITA, but the only solution I can think of is to have a intermediary
server-side script which periodically syncs up with twitter api for new
tweets, stores them locally on the dev's server, and then have client-side
javascript to access the developer's server for tweets.

I guess Twitter wants to get rid of 3rd party clients by doing this... but
I think they're going to lose a lot of developers with this change. (For
me, it was easier to just change to wordpress RSS for my updates)

On Fri, Jun 21, 2013 at 1:24 PM, Remy Sharp [email protected]:

I spent today working on it but hit a blocker. Not sure where I go next
for
now.
On 21 Jun 2013 18:57, "makkynz" [email protected] wrote:

Hi Remy,

Any idea when you will have this fix ready?

—
Reply to this email directly or view it on GitHub<
https://github.com/remy/twitterlib/issues/12#issuecomment-19830964>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-19838650
.

[bebraw]

@RobbyZ That sounds reasonable. It would be pretty easy to set up a Node.js service you can host on, say Heroku, and that acts as a proxy between Twitter and your service. Would this be legal according to Twitter EULA (or whatever they have)?

[remy]

We've (at Left Logic) have created one of those, and already been warned
that Twitter doesn't particular like you doing that: http://twproxy.eu/

On 22 June 2013 10:51, Juho Vepsäläinen [email protected] wrote:

@RobbyZ https://github.com/RobbyZ That sounds reasonable. It would be
pretty easy to set up a Node.js service you can host on, say Heroku, and
that acts as a proxy between Twitter and your service. Would this be legal
according to Twitter EULA (or whatever they have)?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-19854179
.

[bebraw]

Sigh. Such a shame. As I'm not willing to integrate their widget to the site, I'll just drop the custom one. So sad. :(

[tkleijkers]

Guys, just look at this site. You can create a single PHP file which will get the JSON from twitter for you. From javascript just call this file instead of the twitter API.

[ivanoats]

Would a solution using this SO answer's approach be possible?
https://stackoverflow.com/questions/4752168/how-can-i-access-auth-only-twitter-api-methods-from-a-web-application?rq=1

Basically a GET equivalent using oAuth encoded querystring params, which you can use in a cross-domain JSONP call:

https://api.twitter.com/1/friends/ids.json?user_id=254723679&realm=https://api.twitter.com/1/friends/ids.json&oauth_consumer_key=XXXXXXXXXXXXXXXX&oauth_token=XXXXXXXXXXXXXXXX&oauth_nonce=XXXXXXXXXXXXXXXX&oauth_timestamp=1300728665&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_signature=XXXXXXXXXXXXXXXX%3D

Any interest in resuscitating this library with an OAuth get request? I am happy to get a PR started if you think this approach will work.