testing

This is just a test to see how things post when using Microsoft word.

This is probably one of a couple of posts going to be posted to test new plugin configurations. let’s see what this does. Does it tweet and FB faster than twitterfeed? we’ll see.

This is a test to ensure things are showing up on the rss feeds and going where their supposed to when their told to.
I hate broken things.

This *should* post automatically. This thing’s doing what james blog’s post by e-mail functions doing ,and it’s not happifying. roar!
edit from the web: no this did not post automatically, I had to run the script manually.

Shane’s been upgrading, or otherwise breaking, post by email since the start
of forever, and now he may or may not have busted it with Gmail. Yay? So,
one or two minor twists later, we get to see what the Gmail modification
does to non-Gmail email. Yes, it’s geekish. Yes, it’s completely pointless.
But that’s why there’s a testing category. Now, then. Where’d I hide that
send button?

OK.
So I’ve decided that blaming gmail’s fun.
Let’s see if I’ve managed to actually convince the plugin that posts
these that I do like separate lines, even if gmail’s web interface
doesn’t understand the art of sending proper line thingydingies.

This should be a multiline test, if gmail doesn’t fall over. Let’s see what this line looks like.
How about a paragraph?
Do I rule, or does gmail fall on it’s face.
Now, back to your regularly scheduled, stuff? maybe?

This should be a test or we hope it will be a test.

it’s time to break the blog.
this time, via the XML RPC API.
can I track back
locally?
to my own blog. What about
remotely?
to james blog. or do one or both fall flat on the floor.
we’ll soon see.

So now that I’m done failing at life. let’s try this posting by e-mail thing again, k? If this thing falls on the floor again, I’m not gonna be happy.