search

kaihendry / greptweet

Sane twitter backup and search
https://greptweet.com/
Other
76 stars 10 forks source link

Update to authenticated API :( #27

Closed kaihendry closed 11 years ago

kaihendry commented 11 years ago

https://github.com/kaihendry/Greptweet/blob/master/fetch-tweets.sh#L15

https://dev.twitter.com/blog/planning-for-api-v1-retirement

JamieKitson commented 11 years ago

As I understand it, each user does not need to authenticate. You could authenticate the app once and then effectively let everyone else use your token, as long as their feeds are public.

kaihendry commented 11 years ago

From https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline it is a little confusing what needs to happen.

Requires user context is a bit confusing, since the Oauth tool indicates an Access token... and from the FAQ, "We do not currently expire access tokens.". We only need read/access here. I wonder if this means we just need a token and we are away.

https://twitter.com/kaihendry/status/299104954436694016 point to a proxy solution I'm looking at. :/ https://github.com/mojodna/oauth-proxy/issues/2

Need help here.

kaihendry commented 11 years ago

Using this PHP script and jsontool

$ php oauth.php | json -d '|' -a id created_at text
299129791485972500|Wed Feb 06 12:17:54 +0000 2013|Yay, I have a 59LOC PHP script to authenticate with the new 1.1 API @twitterapi #sobs
299113372518055940|Wed Feb 06 11:12:39 +0000 2013|@cheeaun so I don't have to implement that crap in my code? :)

curl → Oauth PHP script xmlstarlet → jsontool