The best of 252,029 bloggers, 223,676 new posts, 327,799 comments, & 54,240,782 words today on WordPress.com.

Those numbers get me far more excited than page views and other “monetization” stats, because these right now front page stats reminds me blogging works.

These stats are about people expressing themselves (writing words) and connecting with other people (commenting).

These are the numbers I look to when I need inspiration.

Melody is a new WordPress competitor — bring it!

Based on Movable Type Open Source (MTOS), Byrne Reese writes “[the project's] focus initially is consciously not about features, but rather upon laying the groundwork through a well-documented set of processes by which future features and contributions can be made.” to live up to it’s tag line “Community Powered Publishing”.

The tag line seems to directly take aim at Movable Type for not being community powered, though in interview Byrne suggests that may be part of the overhead of Movable Type being an enterprise product.

From my position looking over the fence, I’m sympathetic to how the Movable Type community has suffered since “in 2008 [when] the hyper dedicated Movable Type product manager, Byrne Reese, was laid off from Six Apart”. Sure, the MT community isn’t just that one person, but he sure was a catalyst and one of the only open channels to the inners of Six Apart. Since then there doesn’t seem to have been anyone there for the developer community, or for me, as a member of another project, to collaborate with. Even Byrne’s own recent email to the MTOS-dev list asking “Who is the lead engineer of MTOS?” went unanswered. Here is that email:

“I hate to ask such a seemingly odd question, but I have recently had questions I wanted to address to the lead engineer of MTOS — offlist, but am honestly not sure who that might be right now. Who is the best person to address questions about governance and process to? Is there one?”

Mark Carey writes today on mt-hacks.com:

“Over two years ago, Six Apart, the creator of Movable Type open sourced the code for the core Movable Type application. While its was an exciting and bold move, the announcement and product naming choices were confusing to many — the differences between Movable Type Open Source and the Movable Type Commercial product and closed source add-ons sold by Six Apart weren’t easy to grasp, and some even disputed the newly open source nature of core application.”

Although Six Apart promised that they would  continue “fighting for openness” when they announced “Open Source Movable Type ” at the end of 2007, Melody is now the hope for a Movable Type-based openly developed product. The Open Melody FAQs includes:

“The community created Melody out a shared passion for Movable Type and a shared desire to see it flourish as a platform. We felt that the best and quickest way to achieve that goal was to create a product in which the community was inherently entrusted with a greater degree of control over its direction, communication channels and roadmap, and rewarded with more transparency and a greater sense of belonging.”

Serdar Yegulalp writes “To see a new way for the same framework to be improved, and to allow for feedback and suggestions that stem from my own use, is deeply heartening”

I’m very interested to see how the source code flows. The greatest gift of open source isn’t the right to fork, but the ability to merge.

Wih founding members and leadership including the likes of Byrne, Tim Appnel, Jay Allen , and Jesse Gardner, Open Melody is off to an incredible start. ((By incorporating as a US non-profit there commitment is beyond doubt — if only in surviving the painful process that the WordPress Foundation has recently come out the other end of.)) The web site looks great, and they’ve chosen open and friendly development tools.

What is good for blogging and open source is good for WordPress, and Melody seems very good for both:

• I’m eager to put my frustrations trying to collaborate with the often opaque Six Apart behind me, and collaborate through the Open Melody conduit.
• I can’t wait to see a leaner, more modular open source MT based product emerges that is also more feature rich — further confirmation of WordPress’s own approaches, and more good open source products are great for open source.

If you love blogging or open source, then Melody needs our love, participate! (hence this post)

If you are interested, let me know and we can set up a private blog on WordPress.com for you to import into. Bonus is that you will have a backup of your blog ready to go live if anything ever befalls TypePad.

This importer wouldn’t be possible without the heroic effort Ronald Heft Jr put into creating a TypePad AtomPub importer for WordPress — it’s not his fault TypePad still doesn’t have a way to export your full blog.

What’s an AtomPub? While working on this importer Noel contacted TypePad support only to have them tell him they don’t know what AtomPub is, and that they don’t support it.

Anyway, as I said, if you are a TypePad customer, and want to participate in open source development by testing this exporter, or would just like a backup of your blog ready to launch on WordPress.com, leave a comment or send me an email.

There are a couple of things immediately apparent from David’s tweat:

1. He has never exported a blog from TypePad
2. He has never written a blog exporter using AtomPub

Never exported a blog from TypePad

I know this because I’ve done numerous TypePad exports and also working through my customers trying to get support from Six Apart in the export. For most TypePad blogs, it’s impossible to truly export the blog. Six Apart provides no tools or documentation on how to export in a way that preserves the permalinks, and because of a bug in TypePad and an unpublished permalink creation rules that have changed over the years, it guarantees a tedious, manual process to truly export the blog.

About a year ago, I approached members of the Six Apart leadership team in the hopes that they would commit to fix this issue. I was really nice back then and the whole time until recently. Now, I’ve concluded they were playing games.

Six Apart CEO Christopher Alden’s even promised “A Bright New TypePad in 2008“, “TypePad is the only blogging service that gives you complete ownership of your blog”. Appreciate the humor of that? You are trapped on TypePad.

Chris, and all the leadership team will wave their hands, “AtomPub is the answer.”

Never written a blog exporter using AtomPub

Having tried to guide Ronald Heft Jr in creating AtomPub exporters for TypePad and Movable Type, my only conclusion is that no member of Six Apart has written a blog exporter using AtomPub.

Six Apart VP Anil Dash likes to brag about them having helped create Atom and AtomPub. An exporter would have been one of the perfect real world applications to create as part of the creation of the specification. And wouldn’t you think if they were going to tell everyone that is the solution to exporting from TypePad that they would have built such an exporter? They couldn’t have because you can’t without hacking around AtomPub, a lot, which is what Ronald has done.

Then as we had it working, hacks and all, this past weekend, TypePad changed it, fixing one aspect of their AtomPub (drafts are identified), changing a few things that we can adjust to (changed the URL endpoints, switched to MT tag names for consistentency), but also breaking our importer:

• Can no longer retrieve comments on posts.
• No longer contains Pages.
• XML-RPC for trackback retrieval broke.

These issues have been reported to Six Apart and hopefully they will be fixed soon, but there is absolutely zero transparency. There is no way for us to check on the status of these issues.  Wouldn’t you expect the changes to be documented on the “The Official Everything TypePad weblog” and mentioned on “Six Apart Status“?

I cringe to think of the mess it would have been if we had already included the TypePad AtomPub importer in a release.

It seems that independent developers are left out in the cold.

The open web starts at home

Although, I’m excited by the work Ronald is doing, should it really be necessary for TypePad customers to come to the WordPress community to export their blogs?

I’m reminded of Dave Winer’s excellent article “How to do data portability” which includes “The best way to achieve data portability is to just do it”. That article really moved me, data portability, and by extension the open web, starts at your own company, on your own product.

How much longer do TypePad customers have to wait before they can export their blog?

While working on the TypePad and Movable Type AtomPub Exporters (still in progress), programmer Ronald Heft Jr had a problem interacting with the WSSE authentication both use. The problem ended up being in his own code, but it also led to some interesting observations about how the authentication works.

TypePad doesn’t require as secure code.

This is a good reminder that allowing programmers a less secure option, and they will likely take it because they trust you, and have other deadlines.

WSSE authentication is inheritantly insecure.

When Ronald looked in his Movable Type database he found that the passwords were stored in plain text. WordPress remote access development lead Joseph Scott explains that the only way to support WSSE is to store the passwords in plain text on the server, which is one of the reasons why WordPress won’t be supporting WSSE.

I thought it was ripe for parody, and so here is my voice-over:

Update: Six Apart shared my video with all of their customers, but gave no link love or attribution to me (no Lloyd Budd anywhere in sight), see my response “Movable Type Pro, Setting Social Networking Free, Vaporware, WordPress, BuddyPress“