On Sun, Mar 29, 2009 at 11:41 PM, Damon Clinkscales sca...@pobox.comwrote:
How often does this cache update? I'm curious how accurate and reliable
this would be, since
people are constantly modifying their social graph.
In the case of the id/screen_name thing, the data wouldn't change
You can always provide your own cache. It doesn't take that much to
get a complete name-ID cache locally. What does take a lot of calls
is keeping it up-to-date. Since you can change names on ID's it's not
always accurate (though the ID never changes).
It's a huge task to get that initial
On Mar 30, 3:32 am, Jesse Stay jesses...@gmail.com wrote:
On Sun, Mar 29, 2009 at 11:41 PM, Damon Clinkscales sca...@pobox.comwrote:
How often does this cache update? I'm curious how accurate and reliable
this would be, since
people are constantly modifying their social graph.
In
On Sat, Mar 28, 2009 at 11:47 PM, Damon Clinkscales sca...@pobox.com wrote:
see
On Sat, Mar 28, 2009 at 9:16 PM, softprops d.tang...@gmail.com wrote:
It would be nice if the http://twitter.com/[friends|followers]/ids.format
uri's could return a bit more useful info like the screen_name.
If Twitter's going to allow this, why don't they just do it themselves and
provide more accurate and up-to-date info? How often does this cache
update? I'm curious how accurate and reliable this would be, since people
are constantly modifying their social graph.
Alex and crew have already said
On Sun, Mar 29, 2009 at 4:38 PM, Jesse Stay jesses...@gmail.com wrote:
If Twitter's going to allow this, why don't they just do it themselves and
provide more accurate and up-to-date info?
Yeah, that'd be nice. But, given everything going on, it's probably
not a priority right now.
How
see
On Sat, Mar 28, 2009 at 9:16 PM, softprops d.tang...@gmail.com wrote:
It would be nice if the http://twitter.com/[friends|followers]/ids.format
uri's could return a bit more useful info like the screen_name.
[ snip ] ...
?xml version=1.0 encoding=UTF-8?
ids
id
