OAuth with AHK
It no longer seems possible to use httpquery to post a tweet, would anyone be able to provide an OAuth solution for AutoHotkey?
Reference:
<!-- m -->http://blog.twitter.... ... oauth.html<!-- m -->
<!-- m -->http://dev.twitter.com/pages/oauth_faq<!-- m -->
Request Video Tutorials Here or View Current Tutorials on YouTube
Any code ⇈ above ⇈ requires AutoHotkey_L to run
I have a few private scripts that can now no longer tweet status updates which is frustrating
I guess I just have to wait for some smart cookie to come up with a solution. :cry:
It seems that there are a handful of people out there developing "wrappers" in all languages, and everybody else waits for them to do so...
Anyone found a Autohotkey OAuth port?
<!-- m -->http://www.autohotke... ... 084#422084<!-- m -->
<!-- m -->http://www.autohotke... ... 365#423365<!-- m -->
but ideally it should be done via httpquery?
In short, an OAuth is a series of procedures (Server requests, URL-encoding, sorting keys, sending and receiving data, etc.) allowing a user to give the application (script, web app, etc.) access to some functions on his/her account of a specific site, such as Twitter, imgur, etc.
Sometimes coding has the potential to unleash more coding, in a positive sense. By developing an OAuth function for AHK you would enable a great community to do even greater things, communicating with web 2.0. Most site APIs nowdays require OAuth for atleast some of the functions, but there's no current solution for OAuthing with Autohotkey. It also might enable more donationware, and atleast very useful ware, which increases the possibility for donations.
Note that this request is more of a function/library/code request than an application request.
Read more about OAuth and see some Twitter implementation examples here: <!-- m -->http://apiwiki.twitt.../OAuth-Examples<!-- m -->
I really wanna see this happen, but I'm afraid it'd be a bit too much for me. I read it through and it seems doable, but maybe I would need guidance or so. Let's do a community effort?
I think the main problem with OAuth is that it was not designed with desktop applications in mind.
The whole concept is built on the notion that authentication is done in the browser, in the natural environment of the "first party" app.
The fact that it requires a "callback URL" may mean that any desktop app using it may need to run a local web server.
At least as far as I could understand.