RE: [twitter-dev] Twitter Authenication
Hi, You'll want OAuth. Start here: http://dev.twitter.com/pages/auth_overview -- Tatham -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of ken lee Sent: Monday, 4 July 2011 6:02 AM To: Twitter Development Talk Subject: [twitter-dev] Twitter Authenication Hello, I am looking for a mod or a know-how to use their twitter account to sign in to my site. Steps: 1. New user that has twitter account comes to my sign 2. Use Sign in with twitter button to authenticate. 3. Once it is authenticate through twitter, I want to have his twitter's username as the username on my site. As long as it passes back the username, I can assign that username to the signup form on my site. I've been googling google for the know-how, but with little luck. Please advise. Thanks! -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
RE: [twitter-dev] Twitter Rate-limiting on the statuses/friends list?
Just because it doesn't require authentication doesn't mean you can't auth anyway. -- Tatham Oddie au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie If you're printing this email, you're doing it wrong. This is a computer, not a typewriter. From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of A. Kumar Sent: Monday, 4 April 2011 12:30 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Twitter Rate-limiting on the statuses/friends list? Hi, I am building a web application using sign-in with twitter and upon signed in I am showing user's friends followers. It's not another twitpic like service but in the vertical market (CRM space). Since sign-in process api calls are authenticated hence will be charged to the respective user (I am ok here) But the real problem is rate-limiting on the the friends/followers list because GET statuses/friends (http://dev.twitter.com/doc/get/statuses/friends) calls do not requires authentication and calls are deducted from the calling hosts IP address allowance (my website) which are permitted 150 requests per hour which my website will reach in few minutes. Earlier I could have asked for the white-listing from twitter but it's not offered anymore. This features (friends/followers list) is very very important features on my website and without this my website will be toothless. Hence I'm very very frustrated. Can somebody help me how do resolve this issue? Thanks in advance. A Kumar. -- 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] getting historical data for more than 150 / 300 users
If you use their OAuth token for each request, then aren't you counting against their usage limit? You could have 5000 users sign up in an hour. You perform 5000 API calls using 5000 different OAuth tokens. Each API call is one count against each token. Each user now has one less API call left that hour. That's how I understand it ... -- Tatham Oddie If you're printing this email, you're doing it wrong. This is a computer, not a typewriter. -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of fifi Sent: Tuesday, 29 March 2011 9:42 AM To: Twitter Development Talk Subject: [twitter-dev] getting historical data for more than 150 / 300 users How can an app get the historical twitter stream for more than 150 / 300 users in an hour? Those users are all signing up to our service and giving us their Oauth tokens. If more than 150 / 300 sign up in an hour, we can't get their historical data using the REST API because of Twitter's limits. Twitter's streaming API will let us get tweets for that user going forward in time, but won't allow us to see the tweets that are already in their stream. Is there any solution for this use case? We want to offer a service that parses user's twitter streams for statistical data, but if we can't go back and get their historical record, they'll have nothing when they first log in to the site. -- 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] url expansion
http://dev.twitter.com/pages/tweet_entities + http://freenuts.com/top-10-websites-to-expand-any-short-url/ -- Tatham Oddie au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie If you're printing this email, you're doing it wrong. This is a computer, not a typewriter. -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of joelbrave Sent: Sunday, 27 March 2011 1:36 PM To: Twitter Development Talk Subject: [twitter-dev] url expansion is there an api request to deliver tweets with an expanded URL? for instance: http://api.twitter.com/statuses/user_timeline/username.xml?count=1 might give me a url with a tinyurl in it. Is there a way to get that same tweet with an expanded URL instead, using the unauthenticated API? - Joel -- 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] problem with user logging in too quickly?
Dukeman330, This issue is being discussed on this thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1011865585b129b5 It has been a problem for a few days now and Twitter aren't being very energetic to fix it. -- Tatham Oddie au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie If you're printing this email, you're doing it wrong. This is a computer, not a typewriter. -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of Dukeman330 Sent: Wednesday, 23 March 2011 7:08 PM To: Twitter Development Talk Subject: [twitter-dev] problem with user logging in too quickly? I'm running into an issue with my app where if a user logs in and approves my app in less than 10 seconds or so (ie, I go from calling the request_token to calling the access_token endpoint in 10 s), I get an authentication failure on the access_token request. Waiting for a bit before making the access_token request results in the request going through just fine. Any idea what could be causing this problem? Is this an expected behavior? I'd guess that some sort of rate limiting might be at play here, but the documentation specifically says that request_token is *not* rate-limited. Any assistance would be appriciated. If there's any further info that would help anyone out there address my issue, please let me know. -- 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] Integrate Twitter Authentication
Sounds like you might need some Google practice ... http://tweetsharp.codeplex.com/wikipage?title=UserGuidereferringTitle=Documentation -- Tatham Oddie au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie If you're printing this email, you're doing it wrong. This is a computer, not a typewriter. From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of Manish Sadhwani Sent: Wednesday, 23 March 2011 10:56 PM To: twitter-development-talk@googlegroups.com Cc: hax0rsteve Subject: Re: [twitter-dev] Integrate Twitter Authentication Thanks for your special offer... :) But I did it... Thanks again Manish On Wed, Mar 23, 2011 at 5:23 PM, hax0rsteve hax0rc...@btinternet.commailto:hax0rc...@btinternet.com wrote: Certainly I can. My contract rates are GBP 400/day (That's UK sterling). But today you are lucky, because I am having a very special offer. You get one google search for ABSOLUTELY FREE! http://www.google.com/#hl=ensafe=offsa=Xei=V92JTeUUgpiFB5LSpMgOved=0CBYQvwUoAQq=.net+twitter+authenticationspell=1fp=1726cbcbb4bc68a9 GIYF hax0rsteve On 23 Mar 2011, at 06:11, Manish Sadhwani wrote: Hello I have my web application in .net (3.5), Need to add twitter authentication. If user is successfully logged (authenticated) on his twitter account, i just want to logged in my application. Can you please provide the .net code for this. Regards Manish Sadhwani -- 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 -- Manish Sadhwani +919928070709 -- 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: 401 unauthorized
I'm getting this same behaviour on http://ivebeen.to If I wait about 30 seconds before trying to convert the request token to an access token, it all works fine. This happens on both my local machine and on the deployed website - two distinct machines in different locations, timezones, etc. Both machines use network updated time from time.windows.com and I've manually triggered each of them to make sure their time is up to date. On Mar 21, 10:56 pm, Trevor Dean trevord...@gmail.com wrote: Yup, totally stopped working for me as well and my scenario is the same as Joe's too. Any status updates on this issue? On Sun, Mar 20, 2011 at 2:09 PM, akiyoshi rafael.fuk...@gmail.com wrote: Well it stopped working for me as well. My scenario was the same as Joe Mayo's till yesterday. On 20 mar, 13:21, Ninjamonk dar...@stuartmedia.co.uk wrote: well it's stopped working completely now even if I pause. Can someone from twitter let us know the progress of this bug? On Mar 20, 3:28 pm, Joe Mayo mayos...@gmail.com wrote: I'm seeing the same problem with 401's during authentication. I have an app that has worked flawlessly (with no code changes) for months that is now receiving 401's. I'm also have multiple support issues on users experiencing intermittent 401 errors. For some apps, every authentication request results in a 401, but it seems to happen every other authentication for others. Joe On Mar 20, 9:10 am, Ninjamonk dar...@stuartmedia.co.uk wrote: I am still getting this issue and I think it's time related at twitters end. steps: 1. go to twitter and let user auth app 2. on return use verifier and token to ask twitter for the tokens and get a 401 Now if I pause step 2 before asking twitter for the tokens for 10 seconds it works fine. This code has worked for over 6 months and now I am getting this issue all of a sudden. I would look at my code but there are a lot of people getting the same issue. Cheers Darren On Mar 19, 6:05 pm, Matt Harris thematthar...@twitter.com wrote: Hi Trevor, Could you share the request and response you are sending so we can investigate. Remember to obscure user and consumer secrets. Thanks, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Sat, Mar 19, 2011 at 5:47 AM, Trevor Dean trevord...@gmail.com wrote: Is anyone else experiencing any 401 errors all of a sudden? I was doing some testing this morning and was logging in fine using twitter and then 10 min later I started getting 401 unauthorized errors. Thanks, Trevor -- 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-Hidequotedtext - - Show quoted text -- Ocultar texto das mensagens anteriores - - Mostrar texto das mensagens anteriores - -- 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- Hide quoted text - - Show quoted text - -- 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: 401 unauthorized
Please go and star this issue: http://code.google.com/p/twitter-api/issues/detail?id=2118 On Mar 19, 11:47 pm, Trevor Dean trevord...@gmail.com wrote: Is anyone else experiencing any 401 errors all of a sudden? I was doing some testing this morning and was logging in fine using twitter and then 10 min later I started getting 401 unauthorized errors. Thanks, Trevor -- 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: 401 unauthorized
Hi Taylor, I’m using the TweetSharphttp://tweetsharp.codeplex.com/ library. Here are my requests… Getting the request token works: UTC now: 21/03/2011 2:15:44 PM https://api.twitter.com/oauth/request_token GET /oauth/request_token HTTP/1.1 Authorization: OAuth oauth_callback=...,oauth_consumer_key=...,oauth_nonce=...,oauth_signature=...,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1300716944,oauth_version=1.0 User-Agent: TweetSharp Host: api.twitter.com Connection: Keep-Alive 200 OK X-Transaction: 1300716948-77667-49892 X-Runtime: 0.00938 Pragma: no-cache X-Revision: DEV Content-Length: 144 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Content-Type: text/html; charset=utf-8 Date: Mon, 21 Mar 2011 14:15:48 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT ETag: 00fdd191cfa579128843a85a7a58be9f Last-Modified: Mon, 21 Mar 2011 14:15:48 GMT Set-Cookie: k=124.169.147.184; path=/; expires=Mon, 28-Mar-11 14:15:48 GMT; domain=.twitter.com,guest_id=...; path=/; expires=Wed, 20 Apr 2011 14:15:48 GMT,admobuu=...; domain=.m.twitter.com; path=/; expires=Tue, 19 Jan 2038 03:14:07 GMT,_twitter_sess=...; domain=.twitter.com; path=/; HttpOnly Server: hi Vary: Accept-Encoding Keep-Alive: timeout=15, max=100 Connection: Keep-Alive oauth_token=...oauth_token_secret=...oauth_callback_confirmed=true Getting the access token straight away fails with 401: UTC now: 21/03/2011 2:15:46 PM https://api.twitter.com/oauth/access_token POST /oauth/access_token HTTP/1.1 Authorization: OAuth oauth_consumer_key=...,oauth_nonce=...,oauth_signature=...,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1300716946,oauth_token=...,oauth_verifier=...,oauth_version=1.0 Content-Type: application/x-www-form-urlencoded User-Agent: TweetSharp Host: api.twitter.com Content-Length: 0 401 Unauthorized X-Transaction: 1300716950-90707-10498 X-Runtime: 0.00684 Pragma: no-cache X-Revision: DEV Content-Length: 1 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Content-Type: text/html; charset=utf-8 Date: Mon, 21 Mar 2011 14:15:50 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT Last-Modified: Mon, 21 Mar 2011 14:15:50 GMT Set-Cookie: k=124.169.147.184; path=/; expires=Mon, 28-Mar-11 14:15:50 GMT; domain=.twitter.com,guest_id=...; path=/; expires=Wed, 20 Apr 2011 14:15:50 GMT,admobuu=...; domain=.m.twitter.com; path=/; expires=Tue, 19 Jan 2038 03:14:07 GMT,_twitter_sess=...; domain=.twitter.com; path=/; HttpOnly Server: hi Vary: Accept-Encoding Trying the same request again 10 minutes later works (only oauth_timestamp changed): UTC now: 21/03/2011 2:25:42 PM https://api.twitter.com/oauth/access_token POST /oauth/access_token HTTP/1.1 Authorization: OAuth oauth_consumer_key=...,oauth_nonce=...,oauth_signature=...,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1300717542,oauth_token=...,oauth_verifier=...,oauth_version=1.0 Content-Type: application/x-www-form-urlencoded User-Agent: TweetSharp Host: api.twitter.com Content-Length: 0 Connection: Keep-Alive 200 OK X-Transaction: 1300717546-72934-39621 X-Runtime: 0.03056 Pragma: no-cache X-Revision: DEV Content-Length: 163 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Content-Type: text/html; charset=utf-8 Date: Mon, 21 Mar 2011 14:25:46 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT ETag: 9ac6161371b0ee90ef8f6db5322287df Last-Modified: Mon, 21 Mar 2011 14:25:46 GMT Set-Cookie: k=124.169.147.184.1300717546945450; path=/; expires=Mon, 28-Mar-11 14:25:46 GMT; domain=.twitter.com,guest_id=130071754695116305; path=/; expires=Wed, 20 Apr 2011 14:25:46 GMT,admobuu=989196f7fa5728c90e815cc8f97cd56a; domain=.m.twitter.com; path=/; expires=Tue, 19 Jan 2038 03:14:07 GMT,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCMitztguAToHaWQiJTk4NDllMmVhZTM1OTJk%250ANzQ0MGFlMWM2YzQ1ZTU2MDg4IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--dad7912a647454357cfa6f0d07804b5c4b5d6ae4; domain=.twitter.com; path=/; HttpOnly Server: hi Vary: Accept-Encoding Keep-Alive: timeout=15, max=100 Connection: Keep-Alive oauth_token=...oauth_token_secret=...user_id=14051560screen_name=tathamoddie I’m noting that the time offset here is only about 4 seconds, however it certainly takes longer than that to work. You can see this for yourself trying to sign in to http://ivebeen.to -- Tatham Oddie au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie If you’re printing this email, you’re doing it wrong. This is a computer, not a typewriter. From: Taylor Singletary [mailto:taylorsinglet...@twitter.com] Sent: Tuesday, 22 March 2011 1:05 AM To: twitter-development-talk@googlegroups.com Cc: Tatham Oddie Subject: Re: [twitter-dev] Re: 401 unauthorized If you're experiencing this issue, can you please provide these additional details: * are the OAuth URLs you are using http or https? * do your OAuth URLs contain the api subdomain? (you really should be if you aren't) * what OAuth library
