Header Image

The Cheeky Owl

About Myself

I’m a twentytwo twentythree year old student, web developer & web enthusiast living in Switzerland. I study computer science in Rapperswil and work at MIND in Winterthur.

The Twitter REST API v1 is no longer active.

in development

Failed to load resource: the server responded with a status of 410 (Gone) https://search.twitter.com/search.json?q=foo

In disbelief I stared at my Chrome Dev Tools. My jQuery Twitter Plugin had never let me down before. Loyal and faithful it used to serve tweets from a timeline day in, day out. But not so much anymore. In despair, no, in panic I started to track down the issue.
The Twitter REST API v1 is no longer active. Please migrate to API v1.1.
Twitter’s JSON Response said. Oh, well, good on you, Twitter! So I started to look into an alternative jQuery Plugin, one that would work with the REST API v1.1. I couldn’t find one. Did my Google-Fu leave me, as well? No, it didn’t. There’s no easy way to do this.

In version 1.1, we’re requiring applications to authenticate all of their requests with OAuth 1.0a or Application-only authentication.

Well, Twitter are forcing us to either authenticate all our requests with OAuth or use Twitter Widgets. Widgets are not an option, as they allow you no way of custom styles (well except for link colours – isn’t that great?).

I can understand why Twitter would want to authenticate all requests. Nonetheless, I think it’s a shame they’ve robbed us of an easy access to a user’s timeline. Well, let’s do some OAuthing then.

Working on

Oh, a lot of things!