[twitter-dev] Twitter app development require guidance
We are working on Twitter part of this proposed project. we are trying to access twitter from stand alone java application, but got stuck in between. Here is the action flow that we followed. 1. Registered our application with twitter got consumer secrete keys 2. Tried to get request access token with above keys. We got request token but unable to get access token. Before we can get access token its throwing up error.. Suggest some solution please -- 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] Problem using pin method
Hi, I am trying to use twitter in my android application. But i am facing a problem when i logs in and authorize the application it generates a pin and a message to enter that pin. But i am not getting where to enter that pin. -- 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: Problem using pin method
Hi Taylor, Thanks for your response. I have also given a pop up to enter the Pin. But when user enters that pin it does not open any page it just open JSON values.. You can see both the images with following links With input pop up http://picasaweb.google.com/101436805822316575664/TwitterIssue#5562118554484488050 JSON Output http://picasaweb.google.com/101436805822316575664/TwitterIssue#5562118561828800370 On Jan 14, 11:08 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Raj, With PIN mode authorization, your application needs to present a user interface for the end-user to enter the PIN code -- once collected, you send the PIN code as the oauth_verifier to the access token step of OAuth (just like the normal process, except you got the oauth_verifier from the user directly as opposed to a verified OAuth callback). Taylor On Fri, Jan 14, 2011 at 8:35 AM, Raj sunloves...@gmail.com wrote: Hi, I am trying to use twitter in my android application. But i am facing a problem when i logs in and authorize the application it generates a pin and a message to enter that pin. But i am not getting where to enter that pin. -- 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: Seeing weird, malformed HTTP responses? We're on it.
look forward to the fix soon Taylor! -Raj On Jul 19, 1:36 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, Along with a host of other issues we've been keeping you in the loop onhttp://status.twitter.com-- we have another issue that a number of you have pointed out: *Our HTTP responses appear to be insane.* - We're sending Content-Length twice, with differing numbers -- and generally sending duplicate HTTP headers as a whole. - We're sending the incorrect Content-Type corresponding to the response format you are requesting (though the content itself is likely in the format you are expecting). - We're truncating response bodies. We've got the team looking into this right now. It's too early for an ETA on a fix. Thank you for your patience. This is, admittedly, a pretty weird issue. Taylor
[twitter-dev] Re: Slow response to twitter updates for a third party app
Hi John and Ryan, Thanks for looking into this. The good news is that now I am seeing faster responses for my website. I did not change anything on my end, but maybe you guys did, or the traffic was more well-behaved :) In any case, here are my impressions of using the twitter APIs. Use case: Posting updates to Twitter using oAuth API for the case when the consumer app already has the access token. Weekdays mornings (Pacific Time) are generally slower than evenings or weekends. Two timed experiments showed it took 3 sec, and 2 sec for posting two consecutive updates on Monday evening. The first message often takes longer than subsequent updates for the same access token (any token caching going on here ?). Here is a traceroute output taken Monday evening: traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte packets 1 ip-173-201-183-251.ip.secureserver.net (173.201.183.251) 0.918 ms 0.977 ms 1.106 ms 2 ip-208-109-113-169.ip.secureserver.net (208.109.113.169) 1.505 ms 1.490 ms 1.499 ms 3 ip-208-109-113-158.ip.secureserver.net (208.109.113.158) 1.445 ms 1.424 ms 1.412 ms 4 ip-208-109-112-162.ip.secureserver.net (208.109.112.162) 1.386 ms 1.395 ms 1.429 ms 5 ip-208-109-112-138.ip.secureserver.net (208.109.112.138) 1.463 ms 1.515 ms 1.584 ms 6 xe-0-2-0.mpr3.phx2.us.above.net (64.124.196.37) 1.092 ms 1.184 ms 1.142 ms 7 ge-0-3-0.mpr3.lax9.us.above.net (64.125.28.70) 37.857 ms 37.838 ms 37.811 ms 8 xe-0-1-0.er1.lax9.us.above.net (64.125.31.89) 38.317 ms 38.306 ms 38.290 ms 9 xe-0-1-0.mpr1.lax12.us.above.net (64.125.31.189) 9.359 ms 9.476 ms 9.461 ms 10 * * * 11 ae-1.r20.lsanca03.us.bb.gin.ntt.net (129.250.5.253) 10.309 ms * * 12 * * * 13 ae-0.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.96) 89.869 ms 56.178 ms * 14 ae-2.r20.mlpsca01.us.bb.gin.ntt.net (129.250.5.6) 62.913 ms 62.933 ms * 15 * * * 16 128.241.122.117 (128.241.122.117) 60.817 ms 59.320 ms 59.353 ms 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * I would be interested in any pointers you guys might have related to faster response times. Thanks for all your help! -Raj On May 10, 2:51 pm, John Kalucki j...@twitter.com wrote: We're pretty sure that this isn't a connectivity issue. At least, it's not *just* a connectivity issue. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, May 10, 2010 at 2:06 PM, mikawhite mikawh...@me.com wrote: delayed tweet:ping traceroute 64 bytes from 128.242.240.61: icmp_seq=9 ttl=244 time=36.851 ms --- api.twitter.com ping statistics --- 10 packets transmitted, 8 packets received, 20% packet loss round-trip min/avg/max/stddev = 36.851/37.725/39.607/0.902 ms -- traceroute to api.twitter.com (128.242.240.93), 64 hops max, 40 byte packets 1 10.0.1.1 (10.0.1.1) 1.337 ms 0.661 ms 0.678 ms 2 192.168.254.254 (192.168.254.254) 2.009 ms 1.609 ms 0.977 ms 3 dr01.moab.ut.frontiernet.net (74.40.8.109) 8.835 ms 7.860 ms 9.103 ms 4 74.40.41.233 (74.40.41.233) 14.145 ms 13.365 ms 14.576 ms 5 xe--0-2-0---0.cor01.slkc.ut.frontiernet.net (74.40.4.1) 13.959 ms 14.443 ms 14.768 ms 6 ae1---0.cor02.plal.ca.frontiernet.net (74.40.5.61) 34.496 ms 32.226 ms 32.357 ms 7 ae1---0.cbr01.plal.ca.frontiernet.net (74.40.3.170) 60.735 ms 65.466 ms 35.187 ms 8 xe-0.paix.plalca01.us.bb.gin.ntt.net (198.32.176.14) 34.242 ms 36.110 ms 33.274 ms 9 xe-1-1-0.r21.mlpsca01.us.bb.gin.ntt.net (129.250.3.50) 30.914 ms 37.517 ms 30.781 ms 10 mg-2.c20.mlpsca01.us.da.verio.net (129.250.29.81) 34.434 ms 36.171 ms 34.288 ms 11 128.241.122.213 (128.241.122.213) 36.377 ms 34.334 ms 33.771 ms 12 * 128.241.122.213 (128.241.122.213) 34.956 ms !X * 13 * * * -
[twitter-dev] Slow response to twitter updates for a third party app
Hi, I am developing a third party application for posting updates to Twitter for users of my site. I find that the time to post a tweet from my website varies greatly during the day (from 20 seconds to 1 second). I have verified, this long delay is due to a slow response from Twitter. On the other hand, posting an update from another third party website takes only from 6 sec to 1 sec during the day. So my question is: Does Twitter allocate different priorities to third party applications? If yes, what can I do to get a higher priority for updates from my website. Thanks, Raj Kumar
[twitter-dev] Consumer Keys vs IP Address and Domain Name
Does a consumer need new keys from twitter if the server ip address changes, even for the same domain name? I recently upgraded my server from my service provider. As a result the ip address of my server changed, even though the domain name is the same. Now Twitter is not servicing my applications' requests. Do I need new consumer keys?
[twitter-dev] Twitter credentials
1.Is there any twitter api method (php) to get credentials both username and password 2.How to use oauth_token returned in call back url, with this token is there any way to get twitter credentials both username and password, Thanks for your help in advance!
[twitter-dev] Re: Process every single Tweet.
Thanks a lot for your reply, Bjoern. ***from twitter api wiki*** statuses/public_timeline Returns the 20 most recent statuses from non-protected users who have set a custom user icon. The public timeline is cached for 60 seconds so requesting it more often than that is a waste of resources. ***end of api wiki So it is not random according to the documentation. The docs say that they do cache the responses for about a minute, yet i can see new data every 2 seconds.(NOT enough). And the server has already been whitelisted. 20K requests is not gonna be enough for this anyway. Sneaking into - I am not sure that would solve any of the problems. On Jul 17, 5:28 pm, Bjoern bjoer...@googlemail.com wrote: On Jul 17, 1:57 pm, CreativeEye creativv...@gmail.com wrote: 1) Get Twitter Public timeline repeatedly. My understanding is that this does not give you all tweets, just a random selection. 2) Get follower network - user profiles and get their statuses. You would reach the API limit quickly, I'd expect. I don't remember the robots.txt definition very well, but I think twitter also disallows classic web crawlers:http://twitter.com/robots.txt I do know Firehose is an option, but that would again be something like Approach 1. right? Firehose is only an option if Twitter allows you to use it. Please guide me how to proceed. I think there is no reliable way to get ALL tweets, though I would be pleased to learn otherwise. (with the exception of the Firehose, which I suppose one can not plan for). Maybe by being sneaky about it one can get a lot of tweets. For example by getting people to use your service to access twitter, so that you are using up their API limits, not your own. Or at least get the service whitelisted so that you can make lots of requests (I doubt they would be enough to get ALL tweets, though).
[twitter-dev] Re: Process every single Tweet.
@sv - Not quite what i am looking for. But thanks a lot for the link. I think firehose is the only way to go, but thats something not very much in control. @jkalucki - Thanks for your info. I will move to streaming API. I did not know the current approach would be frowned upon. And hopefully hosebird would come out of its cocoon and serve us soon. Search API would not fit into my requirements. Thanks a lot. On Jul 17, 9:38 pm, SV shl...@gmail.com wrote: This could help -http://www.flotzam.com/archivist/ On Jul 17, 6:57 am, CreativeEye creativv...@gmail.com wrote: Myself and my friend are doing a research based on twitter. We need to analyse each and every tweet real time. Can you guide how to approach this. There could be 2 ways of doing this (without Firehose): 1) Get Twitter Public timeline repeatedly. Thankfully Twitter's caching has not been problem to me, they seem to fetch me new data every request. But there are a lot of limitation for this: According to TweeSpeed.com: - Rate of New tweets in the Twitter Server is right now (Wed Jul 17 11:47:02 - GMT) at 9233 tweets/minute. - Ranges between 7K to 20K on an average Weekday. - On June 26 (MJ's death) - reached 25K tweets/minute. Let us now consider the limitation of API requests per hour. - Currently @ 20K per hour. - 1 Req = 20 Tweets - Need 1K Req per minute = 60K req per hour. To Use 1K Requests per minute, we should be using around 17 requests per second. But my server is able to process only 28-33 requests/ minute. Is this the right way to proceed, or am I fundamentally wrong on the approach. 2) Get follower network - user profiles and get their statuses. Frequency of request their new status updates could be set against their general update frequency. But this is Google-like old way of indexing things, which does not quite stand today in the REAL TIME twitter. I do know Firehose is an option, but that would again be something like Approach 1. right? Please guide me how to proceed.
