Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers
Thanks!! - Original Message - From: "John Kalucki" 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 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 wrote: > 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 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. > > One more question about user streams: when @bob sends a tweet to @carol, > I only see that tweet in the web application if I am following *both* > @bob and @carol. Is the same true for user streams, or will I see the > tweet if I'm only following @bob? > > -- > 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 >
Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers
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 wrote: > 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 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. > > One more question about user streams: when @bob sends a tweet to @carol, > I only see that tweet in the web application if I am following *both* > @bob and @carol. Is the same true for user streams, or will I see the > tweet if I'm only following @bob? > > -- > 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 >
Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers
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 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. One more question about user streams: when @bob sends a tweet to @carol, I only see that tweet in the web application if I am following *both* @bob and @carol. Is the same true for user streams, or will I see the tweet if I'm only following @bob? -- 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
Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers
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 already have. ;-) > > 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. I guess it's too soon to think about compressed or binary streams. I'm compressing the JSON (every hour) so compressing would save me bandwidth and processing power. I might not compress binary, though - the JSON is compressing in the range of 7-10 to 1 and I doubt if binary would be that good. -- 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
Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers
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 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 >
[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 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
