Yeah, I would go do far as to say that WordPress made something inherently difficult look easier than it actually is (in addition to some parts which really are easier: as in, there are two metrics, and the former was lowered in an amount much greater than the latter), causing a bunch of people to mistakingly believe that they can handle it themselves; sometimes, a weird configuration file format, or a requirement that you get four pieces separately and stitch them together, is not making something harder for no good reason: it is a subtle indication that helps people understand when they are getting in over their head.

I liken it to the idea that the Infested Forest should look as dark and imposing as it is dangerous: replacing the craggily trees with candy canes and the wolves with golden retriever puppies (still trained to kill, mind you), and carefully laying a golden brick road through the center for easy access with a new sign at the entrance reading "Welcome to the Friendly Forest (Version 2.0)", makes a very dangerous situation look much less scary than it should... the "looking scary enough--or just being difficult enough to navigate--that you don't go in without an RPG party wearing enchanted armor carrying Ariadne's thread" was actually a feature, not a bug.

You made me think, "If only there were a host where you could install the software with one click, and it would automatically update itself..." Follow that thread far enough and the line between a blogging service and a hosting service begins to blur.

The real objective, I think, isn't to get everyone hosting their own stuff, but to popularize technologies that both allow data portability (you can move to another service), and are easy to use.

But WordPress has kind of already done this. They have step-by-step directions[1] for moving from a WordPress.com blog to a self-hosted install.

People who prefer Tumblr (an example of a blog host without an export function) to WordPress do so for reasons that seem orthogonal to data portability:

1. simpler, even easier to use,

2. aesthetics (sleeker design),

3. social networking features built in,

4. reach (because of #3, it's a lot easier to accumulate readers and engagement).

In theory, a service with an open-source codebase, or support for a standard export format, could provide all this. In practice, one hasn't.

Edit: icebraining pointed out downthread that you can mostly export a Tumblr blog by adding '/rss' to the URL of each page, a process that is easily automated.

[1] http://en.support.wordpress.com/moving-a-blog/#moving-to-wor...