Re: [twitter-dev] Twitter search / streaming API limitation query
Hi Taylor, Thanks for your suggestions. We want to use twitter data to provide a user-oriented search based on tweets in a personalised context. The idea to use it from a client is not feasible since, the product is expected to have a thin client i.e. browser. We have developed an algorithm which is expected to sort out tweets based on relevance of the query. Therefore we need to collate the data at the web server. The streaming api does not seem to retrieve older data, and that might well be very relevant, since, lots of queries will require older data in which case a search api query is required. That will hit the ip-address limit. Could any alternative be suggested? Thanks & Regards Umashankar Das On Mon, Jan 10, 2011 at 8:40 PM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > Hi Umashankar, > > Just an additional note that Twitter doesn't yet offer an authenticated > search API -- the Search API is subject to per-IP Address rate limits that > are apart from the rate limits afforded in the standard REST API on > api.twitter.com. If your primary goal is to provide ad-hoc search, then > the unauthenticated Search API will work for a limited amount of queries > (but will require a larger caching infrastructure on your part as you grow). > Another alternative with unauthenticated search is to push the search API > queries to the client (web browser) so that the search query limits apply to > the user's IP address that is utilizing your application. > > If you're going to be tracking multiple search queries and are providing > those tweets for display to your users, then the Streaming API is probably a > better fit. It's wise to consider the end-user-authenticated variations > provided in User Streams and Site Streams (which might be better for your > scenario) http://dev.twitter.com/pages/streaming_api > > What kind of search-based app are you looking to build? > > Taylor > > On Mon, Jan 10, 2011 at 7:00 AM, Umashankar Das > wrote: > >> Thanks, It has been a big help. Looks like twitter does not want to >> respond to me :). >> >> Regards >> Umashankar Das >> >> >> On Mon, Jan 10, 2011 at 3:14 PM, Mauro Asprea wrote: >> >>> I don't know if this would help you but is a nice overview about a) >>> Search vs streaming >>> http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ >>> >>> On Fri, Jan 7, 2011 at 6:32 PM, Umashankar Das >>> wrote: >>> Hi, We are working on a product which will do searches on twitter from a certain server system. We are yet to take a decision whether the searches will be anonymous(Non-authenticated) or authenticated. The decision is subject to limitations on search results using twitter search / streaming apis. I was hoping if you could provide info or references based which provide the information. We hope to have substantial number of unique search (pattern) queries from a particular ip-addresses. Although , the users by themselves are expected to have much lesser queries. We are willing to put a limit of < 30 per hour for the search queries which are authenticated. Please advise on the specs . We do expect that twitter will get many new users after our product is launched. Educated guesses will also be useful for us in making a design decision :) Parameters: a) Search vs streaming b) anonymous vs authenticated Regards Umashankar Das -- 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 >>> >>> >>> >>> -- >>> Mauro Sebastián Asprea >>> >>> E-Mail: mauroasp...@gmail.com >>> Mobile: +34 654297582 >>> Skype: mauro.asprea >>> >>> Algunos hombres ven las cosas como son y se preguntan porque. Otros >>> sueñan cosas que nunca fueron y se preguntan por qué no?. >>> George Bernard Shaw >>> >>> -- >>> 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/Enh
Re: [twitter-dev] Twitter search / streaming API limitation query
Hi Umashankar, Just an additional note that Twitter doesn't yet offer an authenticated search API -- the Search API is subject to per-IP Address rate limits that are apart from the rate limits afforded in the standard REST API on api.twitter.com. If your primary goal is to provide ad-hoc search, then the unauthenticated Search API will work for a limited amount of queries (but will require a larger caching infrastructure on your part as you grow). Another alternative with unauthenticated search is to push the search API queries to the client (web browser) so that the search query limits apply to the user's IP address that is utilizing your application. If you're going to be tracking multiple search queries and are providing those tweets for display to your users, then the Streaming API is probably a better fit. It's wise to consider the end-user-authenticated variations provided in User Streams and Site Streams (which might be better for your scenario) http://dev.twitter.com/pages/streaming_api What kind of search-based app are you looking to build? Taylor On Mon, Jan 10, 2011 at 7:00 AM, Umashankar Das wrote: > Thanks, It has been a big help. Looks like twitter does not want to respond > to me :). > > Regards > Umashankar Das > > > On Mon, Jan 10, 2011 at 3:14 PM, Mauro Asprea wrote: > >> I don't know if this would help you but is a nice overview about a) Search >> vs streaming >> http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ >> >> On Fri, Jan 7, 2011 at 6:32 PM, Umashankar Das >> wrote: >> >>> Hi, >>> We are working on a product which will do searches on twitter from a >>> certain server system. We are yet to take a decision whether the searches >>> will be anonymous(Non-authenticated) or authenticated. >>> >>> The decision is subject to limitations on search results using twitter >>> search / streaming apis. I was hoping if you could provide info or >>> references based which provide the information. We hope to have substantial >>> number of unique search (pattern) queries from a particular ip-addresses. >>> Although , the users by themselves are expected to have much lesser queries. >>> We are willing to put a limit of < 30 per hour for the search queries which >>> are authenticated. >>> >>> Please advise on the specs . We do expect that twitter will get many new >>> users after our product is launched. Educated guesses will also be useful >>> for us in making a design decision :) >>> >>> Parameters: >>> a) Search vs streaming >>> b) anonymous vs authenticated >>> >>> Regards >>> Umashankar Das >>> >>> >>> >>> -- >>> 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 >>> >> >> >> >> -- >> Mauro Sebastián Asprea >> >> E-Mail: mauroasp...@gmail.com >> Mobile: +34 654297582 >> Skype: mauro.asprea >> >> Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan >> cosas que nunca fueron y se preguntan por qué no?. >> George Bernard Shaw >> >> -- >> 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] Twitter search / streaming API limitation query
Thanks, It has been a big help. Looks like twitter does not want to respond to me :). Regards Umashankar Das On Mon, Jan 10, 2011 at 3:14 PM, Mauro Asprea wrote: > I don't know if this would help you but is a nice overview about a) Search > vs streaming > http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ > > On Fri, Jan 7, 2011 at 6:32 PM, Umashankar Das wrote: > >> Hi, >> We are working on a product which will do searches on twitter from a >> certain server system. We are yet to take a decision whether the searches >> will be anonymous(Non-authenticated) or authenticated. >> >> The decision is subject to limitations on search results using twitter >> search / streaming apis. I was hoping if you could provide info or >> references based which provide the information. We hope to have substantial >> number of unique search (pattern) queries from a particular ip-addresses. >> Although , the users by themselves are expected to have much lesser queries. >> We are willing to put a limit of < 30 per hour for the search queries which >> are authenticated. >> >> Please advise on the specs . We do expect that twitter will get many new >> users after our product is launched. Educated guesses will also be useful >> for us in making a design decision :) >> >> Parameters: >> a) Search vs streaming >> b) anonymous vs authenticated >> >> Regards >> Umashankar Das >> >> >> >> -- >> 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 >> > > > > -- > Mauro Sebastián Asprea > > E-Mail: mauroasp...@gmail.com > Mobile: +34 654297582 > Skype: mauro.asprea > > Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan > cosas que nunca fueron y se preguntan por qué no?. > George Bernard Shaw > > -- > 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] Twitter search / streaming API limitation query
I don't know if this would help you but is a nice overview about a) Search vs streaming http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ On Fri, Jan 7, 2011 at 6:32 PM, Umashankar Das wrote: > Hi, > We are working on a product which will do searches on twitter from a > certain server system. We are yet to take a decision whether the searches > will be anonymous(Non-authenticated) or authenticated. > > The decision is subject to limitations on search results using twitter > search / streaming apis. I was hoping if you could provide info or > references based which provide the information. We hope to have substantial > number of unique search (pattern) queries from a particular ip-addresses. > Although , the users by themselves are expected to have much lesser queries. > We are willing to put a limit of < 30 per hour for the search queries which > are authenticated. > > Please advise on the specs . We do expect that twitter will get many new > users after our product is launched. Educated guesses will also be useful > for us in making a design decision :) > > Parameters: > a) Search vs streaming > b) anonymous vs authenticated > > Regards > Umashankar Das > > > > -- > 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 > -- Mauro Sebastián Asprea E-Mail: mauroasp...@gmail.com Mobile: +34 654297582 Skype: mauro.asprea Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan cosas que nunca fueron y se preguntan por qué no?. George Bernard Shaw -- 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
