Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
The streaming API. On 7/20/2010 10:43 AM, PBro wrote: Hi, We are developing an application with which we want to give a message to a user that one of his friends has posted a new tweet. This application is expected to have 40-60 thousand users, so separate api-call's isn't the best option. What would you advise as best practice for retrieving new tweets of a user's friends for this much users? Patrick
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
Yes. GET stream.twitter.com/1/statuses/filter.json follow=userid,userid,userid You'll need to request a higher access level. -John Kalucki htttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Jul 20, 2010 at 7:52 AM, BJ Weschke bwesc...@btwtech.com wrote: The streaming API. On 7/20/2010 10:43 AM, PBro wrote: Hi, We are developing an application with which we want to give a message to a user that one of his friends has posted a new tweet. This application is expected to have 40-60 thousand users, so separate api-call's isn't the best option. What would you advise as best practice for retrieving new tweets of a user's friends for this much users? Patrick
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
Is this a server application (Software as a Service) or do you want this to run on a desktop? If you deployed it as a desktop application, you could use the User Streams capability. The nice thing about User Streams is that you get more than just messages when someone you're following tweets - you get many other events, and you can track by keyword and location as well. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting PBro brouwe...@gmail.com: Hi, We are developing an application with which we want to give a message to a user that one of his friends has posted a new tweet. This application is expected to have 40-60 thousand users, so separate api-call's isn't the best option. What would you advise as best practice for retrieving new tweets of a user's friends for this much users? Patrick
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
We don't allow a single account to follow 60k users, so User Streams isn't going to work. -John On Tue, Jul 20, 2010 at 12:22 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Is this a server application (Software as a Service) or do you want this to run on a desktop? If you deployed it as a desktop application, you could use the User Streams capability. The nice thing about User Streams is that you get more than just messages when someone you're following tweets - you get many other events, and you can track by keyword and location as well. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting PBro brouwe...@gmail.com: Hi, We are developing an application with which we want to give a message to a user that one of his friends has posted a new tweet. This application is expected to have 40-60 thousand users, so separate api-call's isn't the best option. What would you advise as best practice for retrieving new tweets of a user's friends for this much users? Patrick
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
Ah ... I thought he wanted 60K subscribers to each get an alert when one of the people *they* were following tweeted. I suppose 60K users of a User Streams application would put a worse strain on your infrastructure than one Firehose connection, though. ;-) I wasn't aware there was a hard upper limit on how many people a single account could follow. I see quite a few people with tens of thousands of followers that are following roughly the same number of people. So I assumed that if you had 50K or 100K followers, you'd be allowed to follow them all back if you chose to do so. Is that not correct? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting John Kalucki j...@twitter.com: We don't allow a single account to follow 60k users, so User Streams isn't going to work. -John On Tue, Jul 20, 2010 at 12:22 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Is this a server application (Software as a Service) or do you want this to run on a desktop? If you deployed it as a desktop application, you could use the User Streams capability. The nice thing about User Streams is that you get more than just messages when someone you're following tweets - you get many other events, and you can track by keyword and location as well. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting PBro brouwe...@gmail.com: Hi, We are developing an application with which we want to give a message to a user that one of his friends has posted a new tweet. This application is expected to have 40-60 thousand users, so separate api-call's isn't the best option. What would you advise as best practice for retrieving new tweets of a user's friends for this much users? Patrick
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
The trick is getting the 60k followers. On Tue, Jul 20, 2010 at 2:42 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Ah ... I thought he wanted 60K subscribers to each get an alert when one of the people *they* were following tweeted. I suppose 60K users of a User Streams application would put a worse strain on your infrastructure than one Firehose connection, though. ;-) I wasn't aware there was a hard upper limit on how many people a single account could follow. I see quite a few people with tens of thousands of followers that are following roughly the same number of people. So I assumed that if you had 50K or 100K followers, you'd be allowed to follow them all back if you chose to do so. Is that not correct? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting John Kalucki j...@twitter.com: We don't allow a single account to follow 60k users, so User Streams isn't going to work. -John On Tue, Jul 20, 2010 at 12:22 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Is this a server application (Software as a Service) or do you want this to run on a desktop? If you deployed it as a desktop application, you could use the User Streams capability. The nice thing about User Streams is that you get more than just messages when someone you're following tweets - you get many other events, and you can track by keyword and location as well. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting PBro brouwe...@gmail.com: Hi, We are developing an application with which we want to give a message to a user that one of his friends has posted a new tweet. This application is expected to have 40-60 thousand users, so separate api-call's isn't the best option. What would you advise as best practice for retrieving new tweets of a user's friends for this much users? Patrick
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
On Tue, Jul 20, 2010 at 11:54 PM, John Kalucki j...@twitter.com wrote: The trick is getting the 60k followers. The trick is getting 60k users ;)
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
Just give away something valuable to 59,999 for free and the other one will pay all the bills. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Fabien Penso fabienpe...@gmail.com: On Tue, Jul 20, 2010 at 11:54 PM, John Kalucki j...@twitter.com wrote: The trick is getting the 60k followers. The trick is getting 60k users ;)
Re: [twitter-dev] Retrieving new tweets for 40-60 thousand users
http://twitter.com/ModelSupplies ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting John Kalucki j...@twitter.com: The trick is getting the 60k followers. On Tue, Jul 20, 2010 at 2:42 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Ah ... I thought he wanted 60K subscribers to each get an alert when one of the people *they* were following tweeted. I suppose 60K users of a User Streams application would put a worse strain on your infrastructure than one Firehose connection, though. ;-) I wasn't aware there was a hard upper limit on how many people a single account could follow. I see quite a few people with tens of thousands of followers that are following roughly the same number of people. So I assumed that if you had 50K or 100K followers, you'd be allowed to follow them all back if you chose to do so. Is that not correct? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting John Kalucki j...@twitter.com: We don't allow a single account to follow 60k users, so User Streams isn't going to work. -John On Tue, Jul 20, 2010 at 12:22 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Is this a server application (Software as a Service) or do you want this to run on a desktop? If you deployed it as a desktop application, you could use the User Streams capability. The nice thing about User Streams is that you get more than just messages when someone you're following tweets - you get many other events, and you can track by keyword and location as well. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting PBro brouwe...@gmail.com: Hi, We are developing an application with which we want to give a message to a user that one of his friends has posted a new tweet. This application is expected to have 40-60 thousand users, so separate api-call's isn't the best option. What would you advise as best practice for retrieving new tweets of a user's friends for this much users? Patrick
