I've added you to the direct list.
Note that the inference algorithm is quite forgiving, so "twitter @Locke1689", or "@Locke1689 on twitter", or even "twitter: Locke1689" would all have worked out.
About 50 people (from a pool of 1000) with twitter accounts on their profile were left out due to this not so optimal inference.
Hi Alex. I am sorry you were not listed. My first user sources were hnsearch[1][2] and on Twitter Users Most Followed by Readers of Hacker News[3].
I am adding the leader's list to the user discovery, and this should be solved shortly.
[1] http://www.hnsearch.com/search#request/users&q=twitter&#...
[2] http://www.hnsearch.com/search#request/users&q=twitter.c...
[3] http://talkfast.org/2010/07/28/twitter-users-most-followed-b...
Also, I feel left out. :P
As it gets out, people who are interested into being listed can just put "twitter: " before their @twitterusername.
Not being very thorough also allows people to self-exlude from the listing. Which seems be in the interest of some.
How often does the list get refreshed? Or is it live? (if it's live, how are you handling the attention without melting servers)
Also the attention is not that bad (8775 visits so far). Also, heroku's varnish cache on static assets, html page and on Ajax requests is pretty great.
And mixpanel is handling the metrics, so I'm pretty covered.
That's a great point. Can you post info on the site on how to be included or self exclude for those who have a twitter account? (I don't but have considered getting one. I would kind of like to know how to self exclude should I get one. I've had lots of issues over the years with unwanted, negative attention. One of my primary concerns these days is having some control over how much exposure I am getting.)
Thanks so much.
For now, I just make clear that things like "myname on twitter" and "twitter is myname" will never be considered.
However, the biggest problem is finding such users. HNSearchAPI is not complete (for instance, fogus is not listed when you search for "twitter"[1], but is when you search for "twitter.com"[2]).
Which requires quite a lot of crawling (the unnofficial api helps sometimes[3], and sometimes it doesn't[4]). And HN robots is quite restrictive[5]
[1] http://www.hnsearch.com/search#request/users&q=twitter&#...
[2] http://www.hnsearch.com/search#request/users&q=twitter.c...
[3] http://api.ihackernews.com/page
It is updated automatically with time, so people don't need to worry about particular requests.
Edit: In the mean time, I'll probably add support for the entire leaderboard, focusing only the standard HN profile. No photos though...
[1] https://plus.google.com/u/0/101556315529391051445/posts//p/p...
Notice that HNSearch API limits the amount of responses to 1000, but this has nothing to do with the current limit (you can hack this limit by sorting ascending and descending). But the limit was not reached, so I did not need to cheat.
Twitter profiles were focused as not many people mention their github/facebook/stackoverflow profiles.
The reason why the list is similar to the leaderboard is because data is sorted by who has the most karma.