On Mar 30, 3:32 am, Jesse Stay wrote:
> On Sun, Mar 29, 2009 at 11:41 PM, Damon Clinkscales wrote:
>
> > > 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/scree
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 sc
On Sun, Mar 29, 2009 at 11:41 PM, Damon Clinkscales wrote:
> > 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
> much. Ideall
On Sun, Mar 29, 2009 at 4:38 PM, Jesse Stay 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 often does this cach
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 th
Wow! What a great idea. Offloading the burden on twitter's servers/dbs
to a simple id->name cache hosted via another service on someone
elses. I will have to check that out.
On Mar 29, 2:52 pm, Damon Clinkscales wrote:
> On Sat, Mar 28, 2009 at 11:47 PM, Damon Clinkscales wrote:
> > see
>
> > O
On Sat, Mar 28, 2009 at 11:47 PM, Damon Clinkscales wrote:
> see
>
> On Sat, Mar 28, 2009 at 9:16 PM, softprops 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 ] ...
>>
>>
>
On Sat, Mar 28, 2009 at 7:16 PM, softprops wrote:
>
>
> What is the best way to accomplish getting a list a given users
> friends names while pulling the least amount of data?
Given the way things are, the fastest way I've found is to get the user's
status timeline and pull the names from the tw
see
On Sat, Mar 28, 2009 at 9:16 PM, softprops 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 ] ...
>
>
> 1
> 2
>
They aren't going to do this for performance reasons, even
