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 rules fire, you get the same event as everyone else who is party to the event. There are also use cases beyond user streams that require completeness. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, Apr 25, 2010 at 8:18 PM, M. Edward (Ed) Borasky <zn...@comcast.net> wrote: > 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 comments / > questions I have other than unfollows are: > > 1. How do I code the "track" option? Is it done the same way (in curl) > as I would do it for the "filter" endpoint? > > 2. Can I add "locations" as well as "track"? I don't have a use case for > that just yet, mostly because so few tweets near me geographically are > geotagged. But I would certainly use it if it was available. > > 3. I did a test of a direct message. Contrary to popular belief, it *is* > possible to send yourself a DM. Note to self ... ;-) Anyhow, there is a > lot of duplication in the JSON for a DM. It looks like you have user > objects for the sender and receiver and have duplicated some of the data > in those user objects in the DM object. Moreover, on a user stream, one > of the people in a DM is going to be you - why even have your own object > in the message? > > Parsing doesn't look difficult - JSON "documents" are "traditionally" > free-form anyhow, IIRC. > -- > M. Edward (Ed) Borasky > borasky-research.net/m-edward-ed-borasky > > "A mathematician is a device for turning coffee into theorems." ~ Paul Erdős > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >