Re: [twitter-dev] URGENT: Advice on building the correct API stream
I have asked our developers to implement the statuses/filter API stream, however they have come back with the following: 1) We will not be able to fetch previous tweets for the accounts because count parameter can not be used for default role (but can be used for increased access level roles e.g. Birddog, Shadow). 2) Also, if streaming connections is closed (reason can be anything) than we will not be able to fetch the tweets for that connection closed period. So we do also need a monitoring job to monitor the daemon/backgroun process that fetch the tweets. Any help from anyone would be great Thanks Neil On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote: I'm using the streaming API to pull in tweets at that rate for several sites with no problem. The default access level gives you all the tweets for up to 5,000 users. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter From my experience, if you create a useful site for this level of users, you can go back later with a much stronger argument for higher access later. If you are using PHP, I recommend Fenn Bailey's Phirehose library to manage the connection. http://code.google.com/p/phirehose/ If you architect your tweet collection code so that all tweets are put into a normalized database, and the rest of the code only uses the database and not the API, you can easily change to a new type of API connection later. But if all you want now is tweets, the streaming API is good for now. On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com wrote: Great - thanks Tom. For our site we will be pulling in quite few thousand tweets per hour. Do you see any limitation with this API? On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote: Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods http://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Hi Neil, This is where you fallback to the REST API. If you need to catch up you can do so to the best of your abilities (and availability) via REST (as you'll have plenty of remaining API calls since you'll only be using REST for backfill and supplemental metadata). The implementation is not trivial, but it's the best solution for these use cases. It's not the end of the world to miss some tweets here and there. Taylor On Thu, Nov 18, 2010 at 7:03 AM, Neil Sheth sheth.n...@gmail.com wrote: I have asked our developers to implement the statuses/filter API stream, however they have come back with the following: 1) We will not be able to fetch previous tweets for the accounts because count parameter can not be used for default role (but can be used for increased access level roles e.g. Birddog, Shadow). 2) Also, if streaming connections is closed (reason can be anything) than we will not be able to fetch the tweets for that connection closed period. So we do also need a monitoring job to monitor the daemon/backgroun process that fetch the tweets. Any help from anyone would be great Thanks Neil On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote: I'm using the streaming API to pull in tweets at that rate for several sites with no problem. The default access level gives you all the tweets for up to 5,000 users. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter From my experience, if you create a useful site for this level of users, you can go back later with a much stronger argument for higher access later. If you are using PHP, I recommend Fenn Bailey's Phirehose library to manage the connection. http://code.google.com/p/phirehose/ If you architect your tweet collection code so that all tweets are put into a normalized database, and the rest of the code only uses the database and not the API, you can easily change to a new type of API connection later. But if all you want now is tweets, the streaming API is good for now. On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com wrote: Great - thanks Tom. For our site we will be pulling in quite few thousand tweets per hour. Do you see any limitation with this API? On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote: Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods http://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group:
Re: [twitter-dev] URGENT: Advice on building the correct API stream
On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote: I have asked our developers to implement the statuses/filter API stream, however they have come back with the following: 1) We will not be able to fetch previous tweets for the accounts because count parameter can not be used for default role (but can be used for increased access level roles e.g. Birddog, Shadow). If by previous tweets you mean tweets in the past, that is never available with the streaming API. Higher access levels won't give you older tweets either. For past tweets you need to use the search API. But the search API is rate limited, and it tends to fail if many search terms are used, so that is also limited. Frankly, past tweets are not available in large quantities with any portion of the API. 2) Also, if streaming connections is closed (reason can be anything) than we will not be able to fetch the tweets for that connection closed period. So we do also need a monitoring job to monitor the daemon/backgroun process that fetch the tweets. Yes, you should always have a monitor running to verify that the streaming API collection process is still working. There are failures on the order of once a month or more in my experience. This is much better than in the past. These may crash your collection script. The answer is again the search API, which can be used to fill in the missing tweets lost during the failure, but the limitations mentioned above still apply. In general, if you are planning on capturing *all* tweets for a set of words or users, and *never* losing any, you are setting an impossible goal. Aiming for a very high level of accuracy is all you are going to achieve. With the right coding 99% or better is possible. Any help from anyone would be great Thanks Neil On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote: I'm using the streaming API to pull in tweets at that rate for several sites with no problem. The default access level gives you all the tweets for up to 5,000 users. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter From my experience, if you create a useful site for this level of users, you can go back later with a much stronger argument for higher access later. If you are using PHP, I recommend Fenn Bailey's Phirehose library to manage the connection. http://code.google.com/p/phirehose/ If you architect your tweet collection code so that all tweets are put into a normalized database, and the rest of the code only uses the database and not the API, you can easily change to a new type of API connection later. But if all you want now is tweets, the streaming API is good for now. On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com wrote: Great - thanks Tom. For our site we will be pulling in quite few thousand tweets per hour. Do you see any limitation with this API? On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote: Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Quoting Adam Green 140...@gmail.com: In general, if you are planning on capturing *all* tweets for a set of words or users, and *never* losing any, you are setting an impossible goal. Aiming for a very high level of accuracy is all you are going to achieve. With the right coding 99% or better is possible. Perhaps Gnip will be able to supply 99.9% or 99.99%. They've certainly got the infrastructure, according to Pete Warden's writeup in RWW (http://www.readwriteweb.com/hack/2010/11/why-is-twitter-partnering-with-gnip.php) I wouldn't bet on five nines, though. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Hi Adam, Thanks for your advice, just wanted to ask if you have a link to the solution you mentioned for point 2 i.e. the Search API? Regards Neil On 18 November 2010 15:19, Adam Green 140...@gmail.com wrote: On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote: I have asked our developers to implement the statuses/filter API stream, however they have come back with the following: 1) We will not be able to fetch previous tweets for the accounts because count parameter can not be used for default role (but can be used for increased access level roles e.g. Birddog, Shadow). If by previous tweets you mean tweets in the past, that is never available with the streaming API. Higher access levels won't give you older tweets either. For past tweets you need to use the search API. But the search API is rate limited, and it tends to fail if many search terms are used, so that is also limited. Frankly, past tweets are not available in large quantities with any portion of the API. 2) Also, if streaming connections is closed (reason can be anything) than we will not be able to fetch the tweets for that connection closed period. So we do also need a monitoring job to monitor the daemon/backgroun process that fetch the tweets. Yes, you should always have a monitor running to verify that the streaming API collection process is still working. There are failures on the order of once a month or more in my experience. This is much better than in the past. These may crash your collection script. The answer is again the search API, which can be used to fill in the missing tweets lost during the failure, but the limitations mentioned above still apply. In general, if you are planning on capturing *all* tweets for a set of words or users, and *never* losing any, you are setting an impossible goal. Aiming for a very high level of accuracy is all you are going to achieve. With the right coding 99% or better is possible. Any help from anyone would be great Thanks Neil On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote: I'm using the streaming API to pull in tweets at that rate for several sites with no problem. The default access level gives you all the tweets for up to 5,000 users. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter From my experience, if you create a useful site for this level of users, you can go back later with a much stronger argument for higher access later. If you are using PHP, I recommend Fenn Bailey's Phirehose library to manage the connection. http://code.google.com/p/phirehose/ If you architect your tweet collection code so that all tweets are put into a normalized database, and the rest of the code only uses the database and not the API, you can easily change to a new type of API connection later. But if all you want now is tweets, the streaming API is good for now. On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com wrote: Great - thanks Tom. For our site we will be pulling in quite few thousand tweets per hour. Do you see any limitation with this API? On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote: Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Neil: If you mean a link to the Twitter doc on the search API, that is here: http://dev.twitter.com/doc/get/search I've also written a detailed comparison of the search API vs. the streaming API that may help your coders pick the right solution: http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ If you wanted a solution to the specific issue of filling in missing tweets with the search API, I don't know of an example that covers exactly that, but the basic idea is: - Collect tweets with the streaming API and the track parameter for your keywords. Make the id_str of each tweet the primary key of the table where they are stored. - Monitor the created_at value for the most recent tweet added to the database with a cron job that runs every five minutes or so. If tweets arrive less frequently for your keywords, make this a longer interval. - If the monitor script finds that no new tweets have been stored within your test interval, it can use the search API to gather tweets based on the same keywords. The search API returns up to 15 pages of results in reverse date order, with up to 100 tweets per page. So even tweets for active topics will still available from search. - As tweets arrive from search, compare the id_str of the new tweets with those in the database. Add the ones that aren't already there. Your search code should stop making requests when you get to older tweets you already have in the DB. This basically gives you real-time tweets from the streaming API, and automatic back filling for missed tweets with the search API. I've probably exhausted the patience of others on this topic, so contact me directly if you need more help: 140...@gmail.com On Thu, Nov 18, 2010 at 3:05 PM, Neil Sheth sheth.n...@gmail.com wrote: Hi Adam, Thanks for your advice, just wanted to ask if you have a link to the solution you mentioned for point 2 i.e. the Search API? Regards Neil On 18 November 2010 15:19, Adam Green 140...@gmail.com wrote: On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote: I have asked our developers to implement the statuses/filter API stream, however they have come back with the following: 1) We will not be able to fetch previous tweets for the accounts because count parameter can not be used for default role (but can be used for increased access level roles e.g. Birddog, Shadow). If by previous tweets you mean tweets in the past, that is never available with the streaming API. Higher access levels won't give you older tweets either. For past tweets you need to use the search API. But the search API is rate limited, and it tends to fail if many search terms are used, so that is also limited. Frankly, past tweets are not available in large quantities with any portion of the API. 2) Also, if streaming connections is closed (reason can be anything) than we will not be able to fetch the tweets for that connection closed period. So we do also need a monitoring job to monitor the daemon/backgroun process that fetch the tweets. Yes, you should always have a monitor running to verify that the streaming API collection process is still working. There are failures on the order of once a month or more in my experience. This is much better than in the past. These may crash your collection script. The answer is again the search API, which can be used to fill in the missing tweets lost during the failure, but the limitations mentioned above still apply. In general, if you are planning on capturing *all* tweets for a set of words or users, and *never* losing any, you are setting an impossible goal. Aiming for a very high level of accuracy is all you are going to achieve. With the right coding 99% or better is possible. Any help from anyone would be great Thanks Neil On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote: I'm using the streaming API to pull in tweets at that rate for several sites with no problem. The default access level gives you all the tweets for up to 5,000 users. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter From my experience, if you create a useful site for this level of users, you can go back later with a much stronger argument for higher access later. If you are using PHP, I recommend Fenn Bailey's Phirehose library to manage the connection. http://code.google.com/p/phirehose/ If you architect your tweet collection code so that all tweets are put into a normalized database, and the rest of the code only uses the database and not the API, you can easily change to a new type of API connection later. But if all you want now is tweets, the streaming API is good for now. On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com wrote: Great - thanks Tom. For our site we will be pulling in quite few thousand tweets per hour. Do you see any limitation with this
Re: [twitter-dev] URGENT: Advice on building the correct API stream
This is great advice, many thanks. Will keep your blog and personal email address in mind for the future Sent from my iPhone On 18 Nov 2010, at 21:56, Adam Green 140...@gmail.com wrote: Neil: If you mean a link to the Twitter doc on the search API, that is here: http://dev.twitter.com/doc/get/search I've also written a detailed comparison of the search API vs. the streaming API that may help your coders pick the right solution: http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ If you wanted a solution to the specific issue of filling in missing tweets with the search API, I don't know of an example that covers exactly that, but the basic idea is: - Collect tweets with the streaming API and the track parameter for your keywords. Make the id_str of each tweet the primary key of the table where they are stored. - Monitor the created_at value for the most recent tweet added to the database with a cron job that runs every five minutes or so. If tweets arrive less frequently for your keywords, make this a longer interval. - If the monitor script finds that no new tweets have been stored within your test interval, it can use the search API to gather tweets based on the same keywords. The search API returns up to 15 pages of results in reverse date order, with up to 100 tweets per page. So even tweets for active topics will still available from search. - As tweets arrive from search, compare the id_str of the new tweets with those in the database. Add the ones that aren't already there. Your search code should stop making requests when you get to older tweets you already have in the DB. This basically gives you real-time tweets from the streaming API, and automatic back filling for missed tweets with the search API. I've probably exhausted the patience of others on this topic, so contact me directly if you need more help: 140...@gmail.com On Thu, Nov 18, 2010 at 3:05 PM, Neil Sheth sheth.n...@gmail.com wrote: Hi Adam, Thanks for your advice, just wanted to ask if you have a link to the solution you mentioned for point 2 i.e. the Search API? Regards Neil On 18 November 2010 15:19, Adam Green 140...@gmail.com wrote: On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote: I have asked our developers to implement the statuses/filter API stream, however they have come back with the following: 1) We will not be able to fetch previous tweets for the accounts because count parameter can not be used for default role (but can be used for increased access level roles e.g. Birddog, Shadow). If by previous tweets you mean tweets in the past, that is never available with the streaming API. Higher access levels won't give you older tweets either. For past tweets you need to use the search API. But the search API is rate limited, and it tends to fail if many search terms are used, so that is also limited. Frankly, past tweets are not available in large quantities with any portion of the API. 2) Also, if streaming connections is closed (reason can be anything) than we will not be able to fetch the tweets for that connection closed period. So we do also need a monitoring job to monitor the daemon/backgroun process that fetch the tweets. Yes, you should always have a monitor running to verify that the streaming API collection process is still working. There are failures on the order of once a month or more in my experience. This is much better than in the past. These may crash your collection script. The answer is again the search API, which can be used to fill in the missing tweets lost during the failure, but the limitations mentioned above still apply. In general, if you are planning on capturing *all* tweets for a set of words or users, and *never* losing any, you are setting an impossible goal. Aiming for a very high level of accuracy is all you are going to achieve. With the right coding 99% or better is possible. Any help from anyone would be great Thanks Neil On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote: I'm using the streaming API to pull in tweets at that rate for several sites with no problem. The default access level gives you all the tweets for up to 5,000 users. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter From my experience, if you create a useful site for this level of users, you can go back later with a much stronger argument for higher access later. If you are using PHP, I recommend Fenn Bailey's Phirehose library to manage the connection. http://code.google.com/p/phirehose/ If you architect your tweet collection code so that all tweets are put into a normalized database, and the rest of the code only uses the database and not the API, you can easily change to a new type of API connection later. But if all you want now is tweets, the streaming API is good for now. On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth
Re: [twitter-dev] URGENT: Advice on building the correct API stream
The Streaming API to which Brian referred is: http://dev.twitter.com/doc/post/statuses/filter Tom On 11/16/10 10:32 PM, Neil wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp:// dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods http://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Hi Taylor, We are pulling in tweets into our site for various twitter users and displaying their tweets. The part that confuses me is whether we need to build the API stream that Brian described in his email (Statuses/Filter) or the site_streams API as mentioned by our developers? Also, just to check if we don't build the site_streams one, is this something we're going to have to build anyway at a later stage? Regards Neil On 16 November 2010 21:55, Taylor Singletary taylorsinglet...@twitter.comwrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp:// dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
If the only thing you want to do is follow the tweets of some users, your best option is the filter stream. Tom On 11/16/10 11:04 PM, Neil Sheth wrote: Yes - but it looks like the site_streams API (in beta) does the same thing, unless I'm missing something. Just wondering whether we need to ignore Brian's email which was sent a few months back and go for the newer thing. On 16 November 2010 21:53, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: The Streaming API to which Brian referred is: http://dev.twitter.com/doc/post/statuses/filter Tom On 11/16/10 10:32 PM, Neil wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods http://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Great - thanks Tom. For our site we will be pulling in quite few thousand tweets per hour. Do you see any limitation with this API? On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote: Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods http://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Hi, as far as I understand the docs there is no limit on the tweets for stream/filter. However, as a regular user you can only follow up to 5000 users (but you should get all of their tweets). If this limits you, you can apply for Shadow-role to up this limit to more users (20k afair). To answer your question: thousands of tweets per hour should be doable, as long as you don't need to follow more than 5000 users. -d -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
One way to approach this problem: For each user's tweets that you want to track -- do you want to require that user to be an authenticated member of your site and opt-in to having you track their tweets, likely in the context of providing a (mostly private) Twitter client experience on the web for them? If the answer here is yes, then Site Streams is a fantastic choice. However, I think you want to track the publicly created tweets of arbitrary users, whether they are members of your site or not. In this case, Brian's original recommendation to utilize the standard Streaming API's track / follow facilities is best. Like all of our APIs, it does have limitations -- only public statuses are returned, and you can only track up to 5,000 users without enhanced streaming permissions. It's best not to worry about requesting additional access levels until you need them. There are some other limitations around tweet velocity and relative percentages of the firehose, but the use case you've detailed here suggests you'd likely not him them. Taylor On Tue, Nov 16, 2010 at 2:01 PM, Neil Sheth sheth.n...@gmail.com wrote: Hi Taylor, We are pulling in tweets into our site for various twitter users and displaying their tweets. The part that confuses me is whether we need to build the API stream that Brian described in his email (Statuses/Filter) or the site_streams API as mentioned by our developers? Also, just to check if we don't build the site_streams one, is this something we're going to have to build anyway at a later stage? Regards Neil On 16 November 2010 21:55, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp:// dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
I'm using the streaming API to pull in tweets at that rate for several sites with no problem. The default access level gives you all the tweets for up to 5,000 users. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter From my experience, if you create a useful site for this level of users, you can go back later with a much stronger argument for higher access later. If you are using PHP, I recommend Fenn Bailey's Phirehose library to manage the connection. http://code.google.com/p/phirehose/ If you architect your tweet collection code so that all tweets are put into a normalized database, and the rest of the code only uses the database and not the API, you can easily change to a new type of API connection later. But if all you want now is tweets, the streaming API is good for now. On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com wrote: Great - thanks Tom. For our site we will be pulling in quite few thousand tweets per hour. Do you see any limitation with this API? On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote: Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods http://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Thanks D - Shadow-role, no doubt I will need to reference this email when we get there! On 16 November 2010 22:16, yaemog Dodigo yae...@gmail.com wrote: Hi, as far as I understand the docs there is no limit on the tweets for stream/filter. However, as a regular user you can only follow up to 5000 users (but you should get all of their tweets). If this limits you, you can apply for Shadow-role to up this limit to more users (20k afair). To answer your question: thousands of tweets per hour should be doable, as long as you don't need to follow more than 5000 users. -d -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
This is very clear now, thanks for the advice. On 16 November 2010 22:17, Taylor Singletary taylorsinglet...@twitter.comwrote: One way to approach this problem: For each user's tweets that you want to track -- do you want to require that user to be an authenticated member of your site and opt-in to having you track their tweets, likely in the context of providing a (mostly private) Twitter client experience on the web for them? If the answer here is yes, then Site Streams is a fantastic choice. However, I think you want to track the publicly created tweets of arbitrary users, whether they are members of your site or not. In this case, Brian's original recommendation to utilize the standard Streaming API's track / follow facilities is best. Like all of our APIs, it does have limitations -- only public statuses are returned, and you can only track up to 5,000 users without enhanced streaming permissions. It's best not to worry about requesting additional access levels until you need them. There are some other limitations around tweet velocity and relative percentages of the firehose, but the use case you've detailed here suggests you'd likely not him them. Taylor On Tue, Nov 16, 2010 at 2:01 PM, Neil Sheth sheth.n...@gmail.com wrote: Hi Taylor, We are pulling in tweets into our site for various twitter users and displaying their tweets. The part that confuses me is whether we need to build the API stream that Brian described in his email (Statuses/Filter) or the site_streams API as mentioned by our developers? Also, just to check if we don't build the site_streams one, is this something we're going to have to build anyway at a later stage? Regards Neil On 16 November 2010 21:55, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp:// dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Quoting Tom van der Woerdt i...@tvdw.eu: If the only thing you want to do is follow the tweets of some users, your best option is the filter stream. Yep - you now get 5000 users from 'filter' without applying for elevated access, and many more if you qualify for elevated access. In addition, 'filter' currently works with basic authentication as well as oAuth. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
