NBnbpoole·May 5, 2011
Fair enough: you'll have a pull request shortly. ;-)
Edit: Pull request created. https://github.com/jmathai/twitter-async/pull/108
In Quick and simple PHP Twitter login for your site, ideal for your weekend projectjmathai
twitter-async
HTML2010–2011
jmathai / twitter-async · Archived
twitter-async
Twitter-async is a high performance wrapper for Twitter's OAuth API which provides parallel/asynchronous calls. Follow @apiclient for commit updates.
3Distinct people
4Mentions
0Explicit recommenders
524GitHub stars
What to know before exploring
What it is
Twitter-async is a high performance wrapper for Twitter's OAuth API which provides parallel/asynchronous calls. Follow @apiclient for commit updates.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month4 dated mentions
Observed mentions: 2010-01-31 05:30:59 UTC to 2011-05-05 00:12:17 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 2010 | 2010-01-01 00:00:00 UTC | 2010-02-01 00:00:00 UTC | 1 | 0 | 1 |
| Feb 2010 | 2010-02-01 00:00:00 UTC | 2010-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2010 | 2010-03-01 00:00:00 UTC | 2010-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2010 | 2010-04-01 00:00:00 UTC | 2010-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2010 | 2010-05-01 00:00:00 UTC | 2010-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2010 | 2010-06-01 00:00:00 UTC | 2010-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2010 | 2010-07-01 00:00:00 UTC | 2010-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2010 | 2010-08-01 00:00:00 UTC | 2010-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2010 | 2010-09-01 00:00:00 UTC | 2010-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2010 | 2010-10-01 00:00:00 UTC | 2010-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2010 | 2010-11-01 00:00:00 UTC | 2010-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2010 | 2010-12-01 00:00:00 UTC | 2011-01-01 00:00:00 UTC | 1 | 0 | 1 |
| Jan 2011 | 2011-01-01 00:00:00 UTC | 2011-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2011 | 2011-02-01 00:00:00 UTC | 2011-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2011 | 2011-03-01 00:00:00 UTC | 2011-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2011 | 2011-04-01 00:00:00 UTC | 2011-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2011 | 2011-05-01 00:00:00 UTC | 2011-06-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
4 sourcesSecurity note: Check out the following lines, taken from the PHP API client used by this application (https://github.com/jmathai/twitter-async/blob/master/EpiOAut...):
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);
Those lines disable certificate verification: if I can intercept the connection between this client and Twitter, I can present my own, self-signed certificate and the client will still send requests as if I were twitter.com. This completely defeats the purpose of using SSL for connections.
In Quick and simple PHP Twitter login for your site, ideal for your weekend projectIt was a lot of work :). I knew making it usable by others would be as much work as writing it in the first place.
It's definitely not fire and forget. I've been using it for over 4 years so I don't have any plans on ditching it. The main point of documenting it was so others would use it and I can improve on the library.
If you look at another one of my libraries on github (https://github.com/jmathai/twitter-async/issues) you'll see that there have been over 90 issues raised by others which I've resolved. It's what's made that library so solid - hoping for the same here.
In Epiphany, a RESTful micro PHP framework I wrote/use for my startupsI would recommend: http://github.com/jmathai/twitter-async/ - it implements Twitter's OAuth API. Will save you some work.
In Ask HN: Review My (Twitter) App: Follow Ham