Outdated API!

[willis81808]

Every time I try and search anything I get this error:

Searching for locations .. Be patient, I am doing my best.
This can take a while, please hold ...
Error while accessing twitter .The problem was : [{u'message': u'The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.', u'code': 68}]

0 tweets have been retrieved out of a total of 0.
From them, we were able to extract 0 locations.
We encountered 1 errors in total accessing various services.

Is there any fix? Any update that I'm missing? I'm running version 0.1.94 on Windows 7

[jonny47]

Getting the same issue, damn it I can't be creepy.

[stephanvierkant]

Two weeks ago, Twitter has retired API v1: https://dev.twitter.com/blog/api-v1-is-retired

I'm not familiar with Python, but maybe I can try to do some pull requests. You can see some of the changes over here: https://dev.twitter.com/blog/api-v1-retirement-final-dates.

[ilektrojohn]

Hello guys and thank for your comments. I know things are broken and it is because of the new API version of twitter and the old version of tweepy library that creepy is using. Unfortunately I have been in serious luck of development time and/or people interested to assist and be part of the project. I have put all my attention in the new version that includes a massive redesign of the application and it gets harder and harder to provide fixes for the older version. Unfortunately I do not have any roadmap on when the new one is going to be ready

[KraftTears76]

Well, at least I'm not alone.

I downloaded the exe file, for 0.1.94 , and sometimes it works.

Waiting on the new version, then ...

[newt57]

Me too...in fact, I can't even AUTHORIZE via my Twitter account in 1.94 - the Autorization button does not re-direct at all.

[joshuadanpeterson]

Checking in on this - just tried out creepy and experienced the same issues previously voiced in this thread.

[ilektrojohn]

I am targeting a closed beta version for next weekend and a release before / around Christmas of v1.0 that addresses this issue among other improvements. If you want to participate in beta and test out, ping me!

[ilektrojohn]

Close as invalid for now, the soon to be released v1.0 handles this.

[newt57]

I'm in on the beta!

On Mon, Dec 9, 2013 at 4:16 AM, Ioannis Kakavas notifications@github.comwrote:

I am targeting a closed beta version for next weekend and a release before
/ around Christmas of v1.0 that addresses this issue among other
improvements. If you want to participate in beta and test out, ping me!

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

This message is a natural product. The slight variations in spelling and
grammar enhance its individual character and beauty and are not to be
considered flaws or defects.

[ilektrojohn]

@newt57 send me a mail and I will fix you up with an installer.

[newt57]

Thanks!

tnew57@gmail.com

On Tue, Dec 17, 2013 at 9:26 AM, Ioannis Kakavas
notifications@github.comwrote:

@newt57 https://github.com/newt57 send me a mail and I will fix you up
with an installer.

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

This message is a natural product. The slight variations in spelling and
grammar enhance its individual character and beauty and are not to be
considered flaws or defects.