About time. And product. And being more deliberate.
Remember the Quicksilver to WordPress Applescript I wrote a while back?
Well, I’ve ported it to Ruby.
The QSPress.rb works the same as the Applescript version, with a couple of tweaks – you can now set categories, flag if a post should be a draft, and upload files – all from Quicksilver.
The full instructions are in the script itself. Enjoy.
QSPress now supports categories. But, I’m on a funky hotel internet right now, so I won’t be able to upload the new version until I get home tomorrow. We can celebrate then.
Yeah!!! It’s up: QSPress 10 May 2007
After reading LifeHacker’s excellent Beginners Guide to Quicksilver I thought I’d try somethings I haven’t asked Quicksilver to do before. Like shell scripts.
I know I’ve got one lying around – here’s one – my backup script.
Bad idea.
Quicksilver is unresponsive while the script is running and completely ignores my increasingly frantic key invocations. Forcing me to actually use the dock and Finder. Blah.
I noticed this briefly when I was playing around with adding Twitter support to qspress. In the end, I decided to use Alex King’s Twitter Tools plugin because the Quicksilver (via qspress) -> WordPress -> (via Twitter Tools) Twitter publishing flow made more sense than sending to WordPress & Twitter simultaneously.
I’m with Aaron, I don’t quite get Twitter. If you want to know what’s on my mind…read this blog. What I do get about Twitter is really, really fast publishing. The faster, the better.
So, I cooked up a little script (11 lines) to post directly to this blog from Quicksilver. If you’ve got a WordPress blog, or blog that understands the MetaWeblogAPI (though, I’ve only tested it on WP).
So, if you want to twitter on your own blog…download QSPress.
The posts look something like this and hey, no character limits. 😉
More on the QSPress page
LATER:
Eric, I say this script is proof XML-RPC isn’t dead.
Last time I checked, Flickr’s ‘blog this’ was XML-RPC. Copy-and-Paste and XML-RPC are two different things. C-and-P exists because video needs at least one ’embed’ tag and well, that’s hard. Add to that, XML-RPC needs an end-point url and a password, that’s a level of complexity above – ‘here take this code’. They serve two different functions – though the final product looks similar.