Update : All I had to do is replace 1 with 1.1 in my Twitter API endpoint
url for j15e.com, I was already using oAuth. Not very complex after all.
Twitter gracefully dropped dead support of API 1.0, your calls are now being
served a 410 GONE http answer with the folloing explaination :
{"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
}
]
}
The worst thing is JSONP support is also completely dropped and CORS (cross origin resource sharing) requests aren't allowed either (all API calls muse be fully authentified via oAuth).
We were doing client-side request to twitter search API on some websites and that is now a thing of the past. Must use a server-side proxy (thanks Heroku for the free dynos!).
I should update j15e.com to show my timeline using API 1.1, but as I am not very interested in updating old PHP code running on recently acquired AppFog, I think I'll just wait until I find some time to just build a new nicer page.