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 umashankar...@gmail.comwrote: 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-dev] Re: Tweet Button share URL fails on mobile
Thanks Matt for forwarding this issue. As other developers already mentioned, it would be great if Twitter could offer versions of the Tweet Button functionality that work on mobile phones, too. (Like Facebook does with its mobile and touch UI versions of its Facebook Share feature.) Something like this should not be too hard to provide and would certainly increase Twitter integration on mobile sites without requiring each and every mobile site developer to (re-)implement a Twitter app for this. Regards, Thomas On Jan 5, 11:39 pm, Matt Harris thematthar...@twitter.com wrote: The browsers currently supported by the Tweet Button are listed on the Tweet Button FAQ page: http://dev.twitter.com/pages/tweet_button_faq#browser-support At the moment, mobile browsers are not included but they should still avoid confusing behavior. I've asked the engineers to look into the response codes and if necessary make changes. Thanks, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Wed, Jan 5, 2011 at 4:23 AM, thobau tho...@gmx.net wrote: I am evaluating the Tweet Button share URL (http://twitter.com/share? url=...) for usage on mobile phones. When opening the URL on a Nokia N95 with passing some value for the url parameter, I am replied with a Basic authentication login (NOT the twitter web login). I checked what might be the reason by tracing the HTTP requests and responses passed between a (desktop) browser and the twitter service when opening the same URL and noticed the following: When passing no url parameter (or one with empty value), the service returns HTTP status code 403, but returns HTML content nevertheless. When passing non-empty url parameter value, the service returns HTTP status code 401, but returns HTML content nevertheless (and does not return the mandatory WWW-authenticate challenge header). While the 403 is ignored and the content (i.e. invalid URL message) is displayed correctly on both desktop and mobile browsers, the mobile browser on the Nokia N95 reacts to the 401 by replying with a Basic authentication login. Of course, there is no way to pass this challenge successfully. So question is: Why are these HTTP status codes returned at all but not a 200 OK instead? -- 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-dev] Re: Unauthorized 401
I found it out myself. I was still using the old call to http://twitter.com/statuses When I changed this to http://api.twitter.com/1/statuses it worked fine, the unauthorized message disappeared. Cheers, Erik On 7 ene, 14:28, Erik Bloem ejbl...@gmail.com wrote: thanks for your reply Deepa, so what do I have to do when I want to use a fixed PIN? The problem is that if I use oauth_verifier with a temporary token, it will ask me to connect to twitter and have to confirm that the application is allowed to connect to my account. That is not fiable in a permanent integration. Once accepted, it generates a PIN code. With this PIN code it must be possible somehow to connect to Twitter. What is the PIN code used for anyway? kindest regards and txs, Erik On 7 ene, 07:09, deepa nagaraj deepa.23.naga...@gmail.com wrote: no you cannot do like that... for each it will generate oauth_verifier. On Fri, Jan 7, 2011 at 5:32 PM, Erik Bloem ejbl...@gmail.com wrote: Hi to all, when I use a temporary oauth_verifier in a oauth/access_token call, it works ok. Nevertheless, when I use a fixed PIN code obtained, it fails with an Unauthorized exception. What could this mean? PIN is wrong? Do I need to use another call, or use another parameter for the PIN and not the oauth_verifier? Thanks for any reply, Erik -- 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 -- Regards, Deepa- Ocultar texto de la cita - - Mostrar texto de la cita -- Ocultar texto de la cita - - Mostrar texto de la cita - -- 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] replies or retweets?
Hi, I have some problems getting retweets. I am modifying old code that uses replies: http://twitter.com/statuses/replies.xml?... I modified it to http://api.twitter.com/1/statuses/retweets/1.xml?... where the 1 in the 1.xml is the status id (or the since id?). Nevertheless, I get an error Unauthorized... Any ideas? Or is there some other way to get the replies, maybe by an old method using replies? Thanks in advance for any reply, Erik -- 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] Vague rules surrounding the verified account badge
I found the following: The Verified Badge cannot be used unless it is provided by Twitter. Accounts using a badge as part of profile pictures, background images, or in any way implying false verification will be permanently suspended. ( from http://support.twitter.com/groups/31-twitter-basics/topics/111-features/articles/119135-about-verified-accounts ) I fully understand that the badge mustn't be used falsely, but it's the first sentence ...0 The Verified Badge cannot be used unless it is provided by Twitter This doesn't really say whether showing it against genuinely verified accounts is allowed. There is nothing in the display guidelines. Are we allowed to display the badge within search results for Twitter users when the API reports the user as verified? -- 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] Retweet Response Code
In our application, we have implemented retweet function from @Anywhere JS API. However, i see that some of retweets are returning errors because of blocs and some other problems what is the best way to handle these errors? How can we implement a callback mechanism to read the status of the API call? mesut -- 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 mauroasp...@gmail.com 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 umashankar...@gmail.comwrote: 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] Vague rules surrounding the verified account badge
Hi Fabian, Yes, you can use Twitter's Verified Account badge to mark users who have the verified=true attribute on their user object. This part of the Developer terms of service/rules of the road ( II, 4e ) clarifies a bit: Do not use the Twitter Verified Account badge, Verified Account status, or any other enhanced user categorization on accounts other than those reported to you by Twitter through the API. Thanks, Taylor On Mon, Jan 10, 2011 at 3:59 AM, Tim fabianh...@googlemail.com wrote: I found the following: The Verified Badge cannot be used unless it is provided by Twitter. Accounts using a badge as part of profile pictures, background images, or in any way implying false verification will be permanently suspended. ( from http://support.twitter.com/groups/31-twitter-basics/topics/111-features/articles/119135-about-verified-accounts ) I fully understand that the badge mustn't be used falsely, but it's the first sentence ...0 The Verified Badge cannot be used unless it is provided by Twitter This doesn't really say whether showing it against genuinely verified accounts is allowed. There is nothing in the display guidelines. Are we allowed to display the badge within search results for Twitter users when the API reports the user as verified? -- 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
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 umashankar...@gmail.comwrote: 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 mauroasp...@gmail.comwrote: 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 umashankar...@gmail.comwrote: 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
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 umashankar...@gmail.comwrote: 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 mauroasp...@gmail.comwrote: 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 umashankar...@gmail.comwrote: 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 -- Twitter developer documentation and resources:
[twitter-dev] Return number of tweets for an account
Hi, I need to get the total number of tweets an account has. How can this be done? Any help is appreciated. Thank you. -- 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] Reply to a tweet
I heard the new twitter uses API calls as any other third party app. I wanted to know, then how its able to show replies to a particular tweet. It's been always possible to check to which a particular tweet has been replied to, but how to check whether the tweet has been replied. -- राहुल चौबे Rahul Choubey http://www.rahulchoubey.com | http://www.tlinker.com Indore -- 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: Help Getting Started with Site Streams
actual code would be most helpful. On Nov 25 2010, 12:05 am, Nancy Neira n143dra...@hotmail.com wrote: Jay You looking for code patch or the actual code to do streaming? Nancy Date: Wed, 24 Nov 2010 23:53:21 -0500 Subject: [twitter-dev] Help Getting Started with Site Streams From: jay...@gmail.com To: twitter-development-talk@googlegroups.com I am trying to get started with the Site Streams. However, I am having a hard time finding the documentation for getting the stream started. Anyone know where I can find this info or able to provide it? I think I just need to know the names of the params, I can probably figure out the rest. Thanks -- 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] Reply to a tweet
There's currently no specific API offered by Twitter for fetching replies to a particular status. #newtwitter uses an API that isn't completely ready yet called related content/results -- while it often fetches related @replies in a conversation thread, its purpose is expanded a bit beyond that. The API is also still subject to change, periods of unavailability, etc. You can read about it here: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cdc34ae78a2350b8 Taylor On Mon, Jan 10, 2011 at 11:42 AM, rahul choubey rahul.chou...@gmail.comwrote: I heard the new twitter uses API calls as any other third party app. I wanted to know, then how its able to show replies to a particular tweet. It's been always possible to check to which a particular tweet has been replied to, but how to check whether the tweet has been replied. -- राहुल चौबे Rahul Choubey http://www.rahulchoubey.com | http://www.tlinker.com Indore -- 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-dev] getting to the twitter homepage with Oauth access token
is there a possibility to get to the user's home page on twitter using the access token. something like the access token sent in as a parameter to some twitter URL? -- 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] xAuth access_token returning 1-length 401 response
I'm trying to to get xAuth to work with my application, using libcurl and a modified TwitCurl engine. Whenever I attempt to obtain an access token, I get a 401 error that contains a single space character (0x20) and nothing else, which is extremely unhelpful. Whenever I try to do other things that shouldn't work (like setting a status without a token), the 401 error returns a useful message, so I'm pretty sure my system is working fine. Can someone point out what I'm missing here? Thanks. Here's what I'm sending to the Twitter servers... URL https://api.twitter.com/oauth/access_token HTTP Header OAuth oauth_consumer_key=cmPTwoVnltXa2N8FAgepw, oauth_nonce=12947058132c2, oauth_signature=6nWCiAN9vg4UYXtaLqh7FLFuq7E%3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1294705813, oauth_version=1.0 Data x_auth_mode=client_auth%26x_auth_password%3DMYPASSWORD %26x_auth_username%3DMYUSERNAME Signature Base POSThttps%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_tokenoauth_consumer_key%3DcmPTwoVnltXa2N8FAgepw %26oauth_nonce%3D12947058132c2%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1294705813%26oauth_version%3D1.0%26x_auth_mode %3Dclient_auth%26x_auth_password%3DMYPASSWORD%26x_auth_username %3DMYUSERNAME And here's what I'm seeing in my logs: * About to connect() to api.twitter.com port 443 (#0) * Trying 128.242.240.253... * connected * Connected to api.twitter.com (128.242.240.253) port 443 (#0) * SSL connection using DHE-RSA-AES256-SHA * Server certificate: *subject: serialNumber=Zys2dJJ09EPoEVGXYtegIdxG3OZtEOib, C=US, O=*.twitter.com, OU=GT57932074, OU=See www.rapidssl.com/resources/cps (c)10, OU=Domain Control Validated - RapidSSL(R), CN=*.twitter.com *start date: 2010-07-13 10:40:16 GMT *expire date: 2011-08-15 12:55:17 GMT *subjectAltName: api.twitter.com matched *issuer: C=US, O=Equifax, OU=Equifax Secure Certificate Authority *SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. POST /oauth/access_token HTTP/1.1 Host: api.twitter.com Accept: */* Content-Length: 85 Content-Type: application/x-www-form-urlencoded HTTP/1.1 401 Unauthorized Date: Tue, 11 Jan 2011 00:25:19 GMT Server: hi Status: 401 Unauthorized X-Transaction: 1294705519-89572-46458 Last-Modified: Tue, 11 Jan 2011 00:25:19 GMT X-Runtime: 0.00697 Content-Type: text/html; charset=utf-8 Content-Length: 1 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Set-Cookie: k=38.98.60.253.1294705519623615; path=/; expires=Tue, 18- Jan-11 00:25:19 GMT; domain=.twitter.com Set-Cookie: guest_id=129470551976790627; path=/; expires=Thu, 10 Feb 2011 00:25:19 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJhsdnItAToHaWQiJWFjZDlkNWQ2YmNkOTc0%250ANmU0ZTkxNzlmZjdlMGQ0OWUxIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--075877d72b9a221a932648a45490dab951649d50; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close * Closing connection #0 -- 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
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, I'm noticing about a 25% loss rate when tracking multiple hashtags vs. using the good old Search API. I'm fouind it hard to believe this is true, so I tested over and over, but I keep getting the same results. The Streaming API just seems to not provide a fair number of tweets. Note that I have the lowest rate limit with the Streaming API -- perhaps highest rate limits have lower loss rates. Has anyone else noticed the rate loss Streaming vs. Search API? Or am I on crack? Does the loss rate get lower with the higher Streaming API account limits? Brian Maso -- 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] Re: ~25% loss rate Streaming API vs. Search API
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, Twitter http://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, I'm noticing about a 25% loss rate when tracking multiple hashtags vs. using the good old Search API. I'm fouind it hard to believe this is true, so I tested over and over, but I keep getting the same results. The Streaming API just seems to not provide a fair number of tweets. Note that I have the lowest rate limit with the Streaming API -- perhaps
Re: [twitter-dev] Reply to a tweet
Thanks much Taylor.appreciate it :) On Tue, Jan 11, 2011 at 3:23 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: There's currently no specific API offered by Twitter for fetching replies to a particular status. #newtwitter uses an API that isn't completely ready yet called related content/results -- while it often fetches related @replies in a conversation thread, its purpose is expanded a bit beyond that. The API is also still subject to change, periods of unavailability, etc. You can read about it here: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cdc34ae78a2350b8 Taylor On Mon, Jan 10, 2011 at 11:42 AM, rahul choubey rahul.chou...@gmail.comwrote: I heard the new twitter uses API calls as any other third party app. I wanted to know, then how its able to show replies to a particular tweet. It's been always possible to check to which a particular tweet has been replied to, but how to check whether the tweet has been replied. -- राहुल चौबे Rahul Choubey http://www.rahulchoubey.com | http://www.tlinker.com Indore -- 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 -- राहुल चौबे Rahul Choubey http://www.rahulchoubey.com | http://www.tlinker.com Indore -- 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
