I’ve rewritten PushPin, my Atom Publishing Protocol client. I’ve moved from Camping to Rails, giving the application some much-needed structure.

Major new features:

• stored passwords are encrypted with AES
• media collections
• service document autodiscovery
• AuthSub (I’m not sure if RFC 5023 support has been pushed onto mainline Blogger yet, though)

The UI should be much more polished, too (although there’s still lots of room for improvement).

Since I’ve got this this blog’s comments coming in via AtomPub, they’ll be broken until I implement OAuth.

Instead of studying, I added rudimentary hReview support to PushPin. Try it out.

It’s starting to get kind of big; may be time to graduate from Camping to Rails.

PushPin is a web-based Atom Publishing Protocol client. The goal is to provide a simple way for users to work with the Protocol, but the really nice thing about it is that it allows you (the server developer) to stop worrying about all those users who haven’t got a client.

Right now it creates, edits and deletes entries. If you’ve logged in with your OpenID, it will store your authentication details and list of collections. The basics are there but there’s still a lot to do.

I’ve put up a test collection that demonstrates how it can be used inside another web app, acting as sort of a web forms ↔ Atom gateway. More on that when things have stabilised.

Please, give it a spin. I haven’t set up any sort of bug tracking yet, so send suggestions and bugs directly to me.

Things that are coming in the vague future:

• grabbing collections from introspection documents
• app:draft and the Slug: header
• a variety of purpose-specific entry editors (eg. WYSIWYG, hReview, …)