I need to write a windows service


#1

Years ago I wrote a proof of concept twitter application that was a Windows Service and it was written in C#.Net. Recently, I’ve been asked to dust it off and finally implement it. In the original application, the config file contained the account username and password ands the developer keys and such. That was before oAuth…

Before I jam a pencil in my eye, is this going to be possible at all with this oAuth crap? As a windows service, running on a remote server, it absolutely must fire up and start performing twitter api stuff on its own without any user intervention. Is this at all possible?

Where is a good high level overview of oAuth?

Where is a good discussion of oAuth implementation for dot net languages?

Thanks in advance.

~ RWA Developer Team


#2

The documentation on this site has sections on OAuth and links for good resources (https://dev.twitter.com/docs/auth/oauth). If you don’t want to write all the OAuth code yourself, check out the available open-source libraries that also support OAuth (https://dev.twitter.com/docs/twitter-libraries#dotnet).

I wrote LINQ to Twitter, which also supports OAuth (http://linqtotwitter.codeplex.com/). There’s documentation that explains OAuth and how to use it with LINQ to Twitter. In your case, since you’re doing a Windows Service, you won’t be needing (or want to) perform the OAuth workflow. Instead, Twitter supports what’s called Single User Authorization, which is the SingleUserAuthorizer in LINQ to Twitter. Essentially, create your application (on this site) and load the SingleUserAuthorizer.Credentials with the consumer key, consumer secret, access token, and access token secret, which you can find on your application page. Then you’ll be set to work with Twitter.

Joe


#3

Thank you for your response. Thank you for pointing me to single user authentication. I will be using your LINQ to Twitter.

~RWA Developer Team


#4

Thank you for pointing me to single user authentication