Comments on: Letting your users “Sign In With Twitter” with OAuth

By: Computers & Web Development Stuff (Links) | Joel Rodrigues

Computers & Web Development Stuff (Links) | Joel Rodrigues — Fri, 23 Jul 2010 18:27:27 +0000

[...] Jaisen Mathai: Letting your users “Sign In With Twitter” with OAuth http://www.jaisenmathai.com/blog/2009/04/30/letting-your-users-sign-in-with-twitter-with-oauth/ [...]

By: Server-side Twitter client possible with OAUTH? | The Largest Forum Archive

Server-side Twitter client possible with OAUTH? | The Largest Forum Archive — Fri, 02 Jul 2010 02:02:07 +0000

[...] Callback method. You are redirected to Twitter, (login if isn’t), click allow access, get redirection back to your callback URL. [...]

By: jaisen

jaisen — Mon, 07 Dec 2009 05:38:44 +0000

Fyi, I’m going to close comments on this post. It’s already got 256. If you have questions regarding the library please redirect them to Github by opening an issue.

http://github.com/jmathai/twitter-async/issues

By: jaisen

jaisen — Mon, 07 Dec 2009 05:34:04 +0000

This is a problem with PHP’s max integer value being exceeded. My suggestion is to convert the integers returned in the response to be strings prior to json_decode’ing. Replace line 214 in
http://github.com/jmathai/twitter-async/blob/master/EpiTwitter.php#L214 with the following.

    $this->responseText = preg_replace('/"(next|previous)_cursor":(-?[0-9]+)/', "\"$1_cursor\":\"$2\"", $this->__resp->data);

I’ve been running with this in production for a couple months with no issues. Haven’t yet considered adding it to the library as a patch.

By: Harry

Harry — Mon, 07 Dec 2009 05:27:21 +0000

when we try to get the followers for some twitter user, the next_cursor we got is in scientific format, and is not usable for next request. here is the code:

    $twitter_obj = new EpiTwitter();
    $search = $twitter_obj->get_basic('/statuses/followers.json' , 
                            array('screen_name' => $this->target_screen_name,
                                  'cursor' => intval ($this->cursor)));
    $followers = array_reverse($search->users);
    
    $this->cursor = (string) $search->next_cursor;

when dump the $search object , we got [next_cursor] => 1.32063884154E+18 and in textResponse, it is ok: "next_cursor":1320638841537822006, "previous_cursor":0 seems the lib is converting this value into scientific format. Can you help to debug and fix this? thx Harry

By: Michael

Michael — Fri, 04 Dec 2009 06:56:31 +0000

Thanks Jaisen – I totally did not know that… Gotta love @twitterapi’s consistent API design…. :|

By: jaisen

jaisen — Fri, 04 Dec 2009 03:20:41 +0000

The retweet endpoint is /statuses/retweet/{$id}.json instead of /statuses/retweet.json?id={$id}.

By: Michael

Michael — Fri, 04 Dec 2009 00:48:33 +0000

Using

$pub_response = $twitterObj->post('/statuses/retweet.json', array('id' => $rt));

I still get the same error all the time...

By: Michael

Michael — Fri, 04 Dec 2009 00:30:10 +0000

Any idea?

By: Michael

Michael — Thu, 03 Dec 2009 23:46:04 +0000

Not sure what those weird double escapes were.. I just upgraded to your most current version using Git as you suggested, but I still get : {“request”:”/1/statuses/retweet.json”,”error”:”Not found”}

on trying to retweet using the code above… $rt is absolutely a valid tweet id…

any thoughts?