On Monday, May 17, 2010 06:34:12 am Neal Rauhauser wrote: > I've published a handful of 'unix way' scripts written in perl and > based on Marc Mims' Net::Twitter library. The basic idea was to lower > the barrier of entry for folks who want some simple thing done - say a > unix admin who wants a system to be able to tweet/DM. There are a lot > of things that could be done with this - I've played a bit with > integrating Nagios alerts using this, with making Request Tracker able > to send messages via Twitter, etc. > > > http://github.com/StrandedWind/Simple-Perl-Scripts-For-Twitter > > > These are little things, as they should be, and made to run from > the command line, which is the right way to handle lots of text data. > I'm seeing this stuff on Oauth, I'm absolutely not a web developer in > any sense of the word, and I'm wondering how I preserve the > functionality of these tools across the pending changes. > > > Any thoughts on how to provide a construction kit for command line/ > daemon users would be appreciated.
Yeah, I'm in the same boat - I've pushed out a few Twitter CSV data acquisition tools written around Net::Twitter. I've actually got the oAuth stuff coded up - I use Browser::Open to fire up a browser and then have the user paste the PIN. The oAuth connectivity I'm using is what's already in Net:::Twitter. I suppose if you are opposed to "firing up a browser", you could emulate the browser in HTTP, grab the PIN coming back, etc. That might be worth adding to Net::Twitter, now that I think of it. Marc? Any chance you could add an "oAuth PIN grabber" to Net::Twitter? Email me off-list if you want my oAuth code - it's pretty simple but I'm not going to open source it. -- M. Edward (Ed) Borasky http://borasky-research.net/m-edward-ed-borasky/ @znmeb "A mathematician is a device for turning coffee into theorems." ~ Paul Erdős
