phil ringnalda

Phil, you could easily implement open posting yourself using a second account on blogger (with permissions to add/publish only) and an xml rpc call to the blogger api.

I dont know if you’ve muddled with xml rpc much but its not too bad.. I would even send you some code if you wanted :P

Hmm. Very almost.

Since Ev doesn’t seem in any hurry to implement the metaWeblog API, I’d have to fudge the titles (stick em in the post, and copy them to the title field while moderating), and I’d have to fudge the posted by somehow, too (don’t have an elegant hack for that, right off), and I could live with the fact that third-party posts wouldn’t be drafted like Open Posting did (since it’s not like I’m posting madly, and can’t slow down to moderate a post), so all I’d need to do would be to throw in the code to email me a notification that I need to moderate something.

Oof, that’s easy. I don’t have any reason not to do this, do I? One more for the todo list.

Thanks for the code offer, but I’ve got the PHP classes laying around here somewhere from an aborted try at a dotcomments installer program. Just need to throw it together.

I didnt think you would need the code but i figured you might run out of excuses and get it done :P

heh.

It’s all done but the mail notification and some cleanup (current version looks like ass, only worse). Oh, and I guess some testing, since so far I only posted once to one blog. And I just realized that I didn’t check to be sure I didn’t publish the funny-to-me post.

Okay, working version of Open Post (opens in the 640×480 popup I’ve got planned for it) is ready for testing. Give it your worst, but do remember that every post will be emailed to me, plus I’ll have to delete it from Blogger (unless someone actually posts something publishable), so try to combine your testing into just a couple of dozen posts or so. Thanks.

Feature requests (like, should the post be mailed to the poster, as well as me?), ideas about what to do when the API chokes (email it, repopulate the form, just die like it does now?), and especially a design (yes, I’m design-impaired: view-source, redo it, and send me a copy, please oh please) would be welcome.

Once I get it fairly reasonable, I’m thinking about a metaWeblog API version for MT (and maybe Radio, and didn’t you do metaWeblog or at least a title hack for BBT, ruzz?) so think about what you would want from that, too.

About TheEndOfFree, something broke in the API calls Jason had coded to let people post, and I don’t think he had time to investigate and fix it. Just to let you know the switch back to manual story submissions through e-mail was not done on purpose.

Phil,

I would recommend a redirect to the page, maybe. Becuase I posted now I have to go figure out where the page is :P

What I would do about dead publishes is, add a link for yourself in the email that gets sent to you that if the publish failed (or post) that you can just click the link to resend the info.

I guess this would mean a lot more work, in that, you would need to save the info to a file or something but your handy with xml right :P

The API fix is coming soon, I would expect by July 30, but this has been impacted by the server code update.

Mostly the ”where is it” question is because you’re coming in from a test link, rather than the link in the faq itself, and because I blew off the documentation, which needs to say ”Thanks for the post, which won’t actually be published until I get around to checking on whether it’s something that I want to publish, so don’t wear your mouse out refreshing the page, because it might be days before I get to it, and even then I might not agree with your post and just delete it” (in maybe not quite so many words).

I like the link to resend, though not quite as much as I would if email clients handled long urls better (another script that’s expecting a get rather than a post, and stick the whole post in a url in the email, would be nice).

you dont need a long url. just use a hash code to identify the post in question. Should be simple enough and prevent mucking about by unsavory types :)