ryanfaerman
Twitter REST API v1 is no longer active.
Here's the json returned when using your library.
{"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}]}
Currently, this library is dead, but I hope it's updated, because it was great!
I'll take a look soon and see what I can do to get this working again.
-- Ryan Faerman
On Jun 12, 2013, at 5:11 PM, Stephen [email protected] wrote:
Here's the json returned when using your library.
{"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}]} Currently, this library is dead, but I hope it's updated, because it was great!
— Reply to this email directly or view it on GitHub.
@ryanfaerman I also would love it if you could get this alive again. Was VERY helpful to me. Would even be willing to donate if this gets working with Twitter's new API.
I tried to implement this with the newer API and got a 215 error (bad authentication data). Not sure if the previous API didn't require authentication, but it's required now. Though I'm not a php developer, I'll see if there's anything I can contribute. :)
Yeah it is the OAuth stuff now in the new API, that is being forced, I think it was basically "conditional" before. Like you though I am not a PHP dev, just a tinkerer, but have been playing around trying to get it to work again but have had little luck. I seem to take one small step forward then many steps back.
Some links that may be of help for those trying to help get this fixed. https://dev.twitter.com/docs/auth/oauth https://dev.twitter.com/docs/api/1.1
Thanks :)
Yeah it looks like you need to set up a twitter developer account and use OAuth with someone's twitter account just to be able to search now. There's a few Twitter 1.1 PHP libraries out there, they're a pain, but I'm not sure there's anything you can do about it.