This is just a test of the new micro.blog URL scheme introduced in the latest version of the iOS app using an action from Drafts: microblog://post?text=[[draft]]

@manton Is there any way to post automatically via the URL scheme or do you have hit post?Also, does it support title as well as text for longer posts?

@colinwalker For now, you have to click Post. I thought we'd start with the basics and then add automatic posting, titles, and x-callback-url later.

@colinwalker I've just downloaded your Drafts action.

@devilgate It’s only simple but saves people having to recreate it.

@colinwalker Did you turn traditional comments off on your blog?

@cdevroe Hmm... not intentionally. Thanks for pointing it out, I'll have to have a look at what's happened.

@cdevroe It looks as though it was only for the post which came via the micro.blog app. All others look okay. I’ve enabled them on that post. Any thoughts @manton ?

@colinwalker @cdevroe I've seen this before, but Micro.blog isn't sending any comment-related parameters. Something causes the default to be ignored on the WordPress side, I think.

@manton Some weird XML-RPC thing perhaps?

@colinwalker I'm not sure. Let me know if it happens on your next post too. I don't think it's a bug in Micro.blog, but if it keeps happening we can add a setting to Micro.blog to control it.

@manton Will do. I'm also looking to see if there's something I can add programatically from my side to force comments to be open on new posts submitted via XML-RPC.

@colinwalker @manton Looks like an expected behavior, if the field is totally omitted WordPress uses an internal default for the post type. This should be derived from the wp-admin discussion settings. Is yours unchecked?

@danielpunkass @manton Nope, mine is checked to allow comments on new posts and works fine except for those coming in via this method. It should be inheriting the ‘allowed by default’ setting but isn’t.

@colinwalker I noticed the same thing. No comment field on my Micro.blog posts, only my posts from MarsEdit. Maybe the “status” post type does it?

@colinwalker Ah, funky!