search

ilektrojohn / creepy

A geolocation OSINT tool. Offers geolocation information gathering through social networking platforms.
http://www.geocreepy.com
GNU General Public License v3.0
1.25k stars 303 forks source link

Creepy problem #26

Closed TaylorHays closed 10 years ago

TaylorHays commented 11 years ago

Hey so I was trying to trace this twitter account that's been bullying me and I put in their username in the top part and hit geolocate or whatever and it always comes up with nothing. Then I put it in the lower part and it says that only authenticated users can search other users. Check your settings. Please help me figure out how to work this :( hahah

cmlh commented 11 years ago

Has the user enabled geotagging within their Twitter "Settings"?

ilektrojohn commented 11 years ago

Hi there, the "top part" you mention is the input field you need to use. If the search comes up with no results, it means that a) User has no tweets that contain geolocation information as @cmlh correctly noted or that b) that user's twitter account is protected and you are not following him.

The "lower part" input field is used for searching for people if you do not know their twitter username. As the message implies the search function is available only to users who have authorized cree.py to use their twitter account.

svtewari commented 11 years ago

how do we authenticate creepy for the use for twitter.. I can get a pin

ilektrojohn commented 11 years ago

Did you try clicking on "Authorize creepy" button ?

beyaz811 commented 11 years ago

Using Creepy 0.1.94 on Windows 7 64-bit OS (logged in as local admin), Creepy does not "authorize" with Twitter. No pin is generated. Clicking "Authorize Creepy" within the settings only hangs up as if it were thinking/processing and then nothing happens. I've also tried having Twitter up and logged in on a browser at the same time but to no avail. I know multiple people are having this issue but it seems to be unresolved. Thank you, in advance, Ioannis.

ilektrojohn commented 10 years ago

Close as invalid for now, if this happens again with the soon to be released v1.0 I will reopen it.