Using Vimpress

I’m regaining some functionality I haven’t had for a long time today. Back in the old days, I used to use [Flog](http://www.ralree.com/2006/09/02/changing-up-the-flogging/”) to post to Typo, but that all went away with Mephisto (I couldn’t get XMLRPC to work properly). So, I’m trying [Vimpress](http://friggeri.net/blog/2007/07/13/vimpress). Hopefully, I won’t need to hack together Ultimate Tag Warrior into WordPress 2.8 to get tagging from vim to work.

##Update
It looks like it’s working, as a matter of fact. I installed the [Markdown for WordPress and bbpress](http://mitcho.com/code/) plugin, and immediately my post was fixed up with nice new syntax. Tags work without any additional plugins using WordPress 2.8. Go Vimpress!

##Update 2
As you can probably see on the sidebar, I added a vimpress repository to GitHub, since it was lacking one before. You can now use vimpress simply by performing a git clone git://github.com/hank/vimpress.git .vim. I went ahead and patched it with the custom slug options mentioned in the main vimpress site’s comments. Both versions are available as [tags on GitHub](http://github.com/hank/vimpress/downloads).

##Update 3
I happened to get to wonder how secure XML-RPC was, so I did a nice little wireshark packet capture, and lo-and-behold, there was my password in plaintext HTTP. I was aghast – why couldn’t they do a little HTTP-Digest authentication or something at least? Anyway, after researching what people think of this, and finding only past vulnerabilities in WordPress, not complaints that it’s just a **bad idea to use insecure XML-RPC for blog posting**, I tried putting an s in front of my HTTP. Guess what – ***It Worked!*** I have to give props to Python for having that all built in.

So now, thanks to Site5′s free-to-use server certificates, I can now use XML-RPC securely.