Advertisement
Ford

Example Twitter XAuth request

Apr 10th, 2011
640
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.48 KB | None | 0 0
  1. Email sent to api@twitter.com
  2.  
  3. Application Name: IRCTweet
  4.  
  5. Consumer Key: xxxxxxxxxxxxxxxxxxxxxx
  6.  
  7. Application ID: n/a
  8.  
  9. Application Site: http://www.hawkee.com/snippet/5955/
  10.  
  11. Twitter: http://twitter.com/fordlawnmower
  12.  
  13.  
  14.  
  15. This is a request to have XAuth Turned on for my application.
  16.  
  17.  
  18.  
  19. Currently I am using basic authorization, as many others are, and I am looking forward to forging on to XAuth. OAuth doesn't work for this application, for many reasons, but I will just itemize a few to make this email more readable.
  20.  
  21.  
  22.  
  23. 1. My application is designed to run without the use of a web browser.
  24.  
  25. 2. My application runs inside mIRC and other irc clients. The usefulness of this application centers around it's ability to run within the confines of the irc client without leaving the irc page.
  26.  
  27. 3. My application uses the built in irc clients scripting language. This makes it much more difficult to script because everything must be done at the socket level making XAuth a much better solution.
  28.  
  29.  
  30.  
  31. Just a few words here to assure you that I understand the importance of twitter passwords.
  32.  
  33. I also want to make it very clear that I will not be storing passwords, in any form, with XAuth.
  34.  
  35. First of all, the original application does store the mime encoded user:password combination with a secondary encryption added. I was never happy about this solution.
  36.  
  37. XAuth will allow me to just deal with a token which will be much more secure for the end user. The new XAuth code will not store any passwords.
  38.  
  39. The new code will only store the needed token(s) and the username. The token and user name will be stored in separate encrypted files with a third encrypted file that will contain a secret key that will be used by the program to determine which tokens go with which user names. I addition, the XAuth routines will be compiled in a .dll file that can only be called from the irc client.
  40.  
  41.  
  42.  
  43. About me:
  44.  
  45. I started writing code in the early 80's on a TRS-80.
  46.  
  47. I write in Cobol, Fortran, Pascal, C, Basic, VB, PHP.
  48.  
  49. I am a network technician with 15 years of IT experience.
  50.  
  51.  
  52.  
  53. Active Twitter Projects:
  54.  
  55. http://www.hawkee.com/snippet/5955/
  56.  
  57. http://www.hawkee.com/snippet/7311/
  58.  
  59. http://www.hawkee.com/snippet/6942/
  60.  
  61. http://www.hawkee.com/snippet/5883/
  62.  
  63. http://www.hawkee.com/snippet/6339/
  64.  
  65.  
  66.  
  67. Thanks for your time.
  68.  
  69. I am really appreciate twitters api and all the time and effort put in by the api staff.
  70.  
  71.  
  72.  
  73. BlackJack Ketcham
  74.  
  75. http://twitter.com/fordlawnmower
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement