Re: [twitter-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
Any update on this? It should be really easy to change that 10 to a 0. Meanwhile, hoards of users are needlessly waiting for 10 seconds every time they log in. :) Thanks, Russell -- 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-dev] Twitter feed for corporate website/portal
I have a corporate website/portal that I want to pull in tweets to, but i'm getting a rate limit using the http feed. So I need to explore other options. Do I need to use an authenticated method to get the tweets? Do I really have to register an application to do this, even though it's not really an application and my users will never be entering or changing the twitter account info. It will be a single twitter account that I will be pulling the feed from. Also, my corporate site doesn't have a public address, and registering an application through twitter appears to require a public url. So how can I get around this? Do I have to create a fake application with a public url, just to generate my keys? Thanks for any help on this. -- 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 feed for corporate website/portal
You can use the /statuses/user_timeline API call instead of the feed if you want. This doesn't require authentication, so there is no need to create an app, if you use this call: http://dev.twitter.com/doc/get/statuses/user_timeline But no matter how you get the data, rate limiting will still be the same. There are three ways to address rate limiting: 1. Get the feed or /statuses/user_timeline without authentication at a rate up to 150 times per hour and store the tweets in a database. Then serve tweets to your web page from the database. 2. Create an app that uses OAuth to get the feed or /statuses/user_timeline at a rate up to 350 times per hour. Store and serve from DB as in 1. 3. Use the Streaming API to follow the user account. This uses Basic Auth, so no app is needed. Get the data, store and serve from DB. The streaming API has the advantage of delivering the data in real time with no rate limiting. The point here is that each page load should not call Twitter for data. It should call for your copy of the data. If you decide to use 2, you do need an app to do OAuth. From my experience, the app registration page needs a properly formatted URL, not a valid URL that you own. This means anything that follows the format of http://domain.com will work. You can even use http://twitter.com. -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev On Tue, Jan 11, 2011 at 7:43 PM, TehOne ele...@gmail.com wrote: I have a corporate website/portal that I want to pull in tweets to, but i'm getting a rate limit using the http feed. So I need to explore other options. Do I need to use an authenticated method to get the tweets? Do I really have to register an application to do this, even though it's not really an application and my users will never be entering or changing the twitter account info. It will be a single twitter account that I will be pulling the feed from. Also, my corporate site doesn't have a public address, and registering an application through twitter appears to require a public url. So how can I get around this? Do I have to create a fake application with a public url, just to generate my keys? Thanks for any help on this. -- 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 feed for corporate website/portal
also, check out Twitter Widgets. You can pull in tweets based on search, profile, or list-- so you might be able to use that. Since the request is client side, rate limiting is not going to be as big of an issue. You could also completely customize the UI if needed, both through the form Twitter provides to generate the UI as well as with plain old css. http://twitter.com/about/resources/widgets If you need any help, I would be happy to help you off the list. On Tue, Jan 11, 2011 at 8:08 PM, Adam Green 140...@gmail.com wrote: You can use the /statuses/user_timeline API call instead of the feed if you want. This doesn't require authentication, so there is no need to create an app, if you use this call: http://dev.twitter.com/doc/get/statuses/user_timeline But no matter how you get the data, rate limiting will still be the same. There are three ways to address rate limiting: 1. Get the feed or /statuses/user_timeline without authentication at a rate up to 150 times per hour and store the tweets in a database. Then serve tweets to your web page from the database. 2. Create an app that uses OAuth to get the feed or /statuses/user_timeline at a rate up to 350 times per hour. Store and serve from DB as in 1. 3. Use the Streaming API to follow the user account. This uses Basic Auth, so no app is needed. Get the data, store and serve from DB. The streaming API has the advantage of delivering the data in real time with no rate limiting. The point here is that each page load should not call Twitter for data. It should call for your copy of the data. If you decide to use 2, you do need an app to do OAuth. From my experience, the app registration page needs a properly formatted URL, not a valid URL that you own. This means anything that follows the format of http://domain.com will work. You can even use http://twitter.com. -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev On Tue, Jan 11, 2011 at 7:43 PM, TehOne ele...@gmail.com wrote: I have a corporate website/portal that I want to pull in tweets to, but i'm getting a rate limit using the http feed. So I need to explore other options. Do I need to use an authenticated method to get the tweets? Do I really have to register an application to do this, even though it's not really an application and my users will never be entering or changing the twitter account info. It will be a single twitter account that I will be pulling the feed from. Also, my corporate site doesn't have a public address, and registering an application through twitter appears to require a public url. So how can I get around this? Do I have to create a fake application with a public url, just to generate my keys? Thanks for any help on this. -- 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 -- Peter Denton Co-Founder, Product Marketing www.mombo.com cell: (206) 427-3866 twitter @Mombo_movies twitter - personal: @petermdenton -- 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-dev] Re: ~25% loss rate Streaming API vs. Search API
Hi Matt, Thanks for the explanation. I will file the bug report. I'd like to hear more about the sample size. I've read through the Streaming API docs a lot, and I haven't come across anything specific about the rate limits. Where can I read more? Brian Maso On Jan 10, 5:24 pm, Matt Harris thematthar...@twitter.com wrote: Hey Brian, When you use the Streaming API filter method we will stream to you all the Tweets which match your track terms - up to your allowed sample size. What this means is over the course of a sampling window we apply your track terms to the full firehose, and then return as many results as your sample rate allows. If you exceed your allowed sample size we will return a 'rate_limited' response containing the total number of matched Tweets missed. When matching track terms we apply the 'track' keywords to the raw Tweet text. This is different to the Search API which applies the track terms to the raw Tweet text plus the expanded URL. (The Streaming API doesn't expand URLs because it would delay the delivery of the Tweet). The issue you are describing is not caused by sampling limits or reduced subsets, but is instead due to a retweet parsing issue our engineers are looking into. What appears to be happening is the Streaming API is trying to match against the truncated RT version of the Tweet instead of the original Tweet text. If you file this in our issue tracker we can let you know when the issue is resolved. The issue tracker can be found here: http://code.google.com/p/twitter-api/issues/list Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Jan 10, 2011 at 4:48 PM, Brian Maso br...@blumenfeld-maso.comwrote: Sounds consistent with what I've been seeing. Where did you get your impression of how the streaming API is optimized? I am having a hard time finding any authoritative documentation describing what the powers that be at Twitter *intend* to be included in the stream (as opposed to what they actually *implemented*, which may differ from intentions for a variety of reasons). If what you say is true, it kind of limits to use-cases of the streaming API to a far narrower set than what one would think by reading the Streaming API documentation. There's one section of the documentation that attempts to describe how to implement a system that utilizes the streaming API and avoids missing any tweets. Obviously if the stream of tweets is already a reduced subset, then it doesn't matter very much if you miss a few. Brian Maso On Jan 9, 4:06 pm, Bess bess...@gmail.com wrote: Streaming API is build by Twitter while Search API is build by Startup Summize acquired by Twitter. Search API is rate-limited. If you just use Twitter search feature, you may see everything. Using Search API to display API returned results is limited by your developer API. Streaming API may not show everything b/c it is optimized on the content based on its logarithm. On Jan 9, 2:29 pm, Brian Maso br...@blumenfeld-maso.com wrote: What I did is opened up three separate normal browser tabs in Firefox, each using the Twitter search web interface to search for three different hashtags (#ces, ces11, and nfl -- examples of three tags that should have decent ongoing traffic). At the same time I have an application capturing tweets from the same three hashtags using the streaming API (filter.json? q=#ces,#ces11,#nfl, with appropriate URL encoding). Irregardless of the amount of time, the streaming application captured about 25% fewer tweets. Detailed analysis of the tweet IDs captured by the browsers vs. those captured by the standalone application retrieving tweets via the streaming API verified that there were tweets delivered through the browsers that did not appear through the streaming API. There were no tweets delivered through the streaming API that did not also appear in the set of tweets delivewred through the browsers. I would love it if anyone else would try a similar experiment and report back results. Maybe I'm doing something wrong, or maybe this is an anomaly, or maybe the streaming API just doesn't capture as much -- impossible for me to say. I note that the streaming API documentation doesn't claim an intent to match accuracy with the search API (nor vice versa). At this point I'm thinking to get the greatest accuracy I should be collecting tweets from *both* APIs. Brian Maso On Jan 7, 5:08 pm, Bess bess...@gmail.com wrote: This is hard to believe. Streaming API is an approved API that should not have any limit. It should give you everything without any limit. On the other hand Search API has rate-limitation. Did you use any filter? On Jan 6, 9:42 pm, Brian Maso br...@blumenfeld-maso.com wrote: Hi All, Using the Streaming API,
[twitter-dev] Search Twitter Feed from a group of Twitters
Hi, I am New to the Twitter search API and was wondering if someone can please help me on where to find some guidance on how to use Twitter Search API to find tweets from a group of twitters. Thanks for all the help in advance -- 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
