On 04/25/2010 08:40 PM, John Kalucki wrote:
The user endpoint is very similar to the filter endpoint. We're tuning
the parameters, but, yes, you can track and loc, just as on filter,
but you can't follow.
Duplicated JSON isn't really a big concern, but I'll look into what we
can trim. The
Currently we deliver these to user streams. We'll probably conditional
them, default off, before we go to beta.
On Mon, Apr 26, 2010 at 12:32 PM, M. Edward (Ed) Borasky
zn...@comcast.net wrote:
On 04/25/2010 08:40 PM, John Kalucki wrote:
The user endpoint is very similar to the filter
Thanks!!
- Original Message -
From: John Kalucki j...@twitter.com
To: twitter-development-talk@googlegroups.com
Sent: Monday, April 26, 2010 12:34:35 PM GMT -08:00 US/Canada Pacific
Subject: Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open
To All Developers
On 04/19/2010 11:20 AM, John Kalucki wrote:
Experiment!
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
I think I saw this request go by, so I'll just add my vote for showing
unfollows as well as follows.
I just started testing with curl tonight. So far the only
The user endpoint is very similar to the filter endpoint. We're tuning
the parameters, but, yes, you can track and loc, just as on filter,
but you can't follow.
Duplicated JSON isn't really a big concern, but I'll look into what we
can trim. The markup is rendered once for all receivers. If the
On 04/25/2010 08:40 PM, John Kalucki wrote:
The user endpoint is very similar to the filter endpoint. We're tuning
the parameters, but, yes, you can track and loc, just as on filter,
but you can't follow.
Yeah, I figured I'd be unable to follow another 200 folks on top of the
over 5000 I
