On Thu, Mar 5, 2009 at 7:59 AM, Doug Williams do...@igudo.com wrote:
The second, and less API intensive method to retrieve a list of all screen
names is to page and parse through a user's friends with paginated calls to
the statuses/friends method
I've been trying this out for the last day
Nick,
Are you using a caching layer? Initialization of the cache will of
course be slow since every user will need to be looked up with a
users/show call, but the cache should eventually pay off after the
most active users have been entered.
Doug
@dougw
On Fri, Mar 6, 2009 at 12:46 PM, Nick
Nick,
Have you looked into memcached [1]? Attribute-value pair caching is
what it was designed to do. Perfect for the write-through cache that
is needed here. It will also handle the pesky details like resolution
expiry for you, too. If you would like help, ping me offline, I can
get you started.
Jake,
There are two options. Since I don't know what you've looked into, I'll list
them below.
You can use the social graph API [1] to gain a list of all other friend IDs
in a single call. This method however does not return screen name of a user
as explained in the linked discussion. This is,
On Thu, Mar 5, 2009 at 6:29 AM, JakeS jakesteven...@gmail.com wrote:
I'd like to implement an addressbook or tab-completion for
@replies-- to make it easier for users to send a message to a specific
user without having to type out the whole username. Unfortunately,
there doesn't seem to be
On Thu, Mar 5, 2009 at 7:59 AM, Doug Williams do...@igudo.com wrote:
Jake,
There are two options. Since I don't know what you've looked into, I'll
list them below.
You can use the social graph API [1] to gain a list of all other friend IDs
in a single call. This method however does not
There is an open issue that is related:
New API method request, return friend starting with...
http://code.google.com/p/twitter-api/issues/detail?id=207
There is some discussion of its merit in the bug description itself,
but you should star it if it would suit your needs.
-Chad
On Thu, Mar 5,
Nick,
These methods aren't perfectly complete for every use case, and that's why
we are here discussing them. Note that easily modifies the work necessary
to retrieve the list of IDs. So yes, that is easily done. I then mentioned
the con: that individual API calls to users/show were necessary to
