Here’s a coincidence. Shortly after I decide to abandon my self-hosted WordPress instance for the safety of a site hosted on WordPress.com, John Beckett starts mulling over whether to leave the WordPress walled garden:
As we have seen in recent days with Tumblr, a shoe could come down one day, and change the rules that govern the existence of our words on the internet. If I choose to walk away from a hosted blogging service, am I really taking ownership though? I still won’t own or control the hardware — I still won’t own or control the connection between the hardware and the wider internet. I’ll just have moved the goal-posts a little closer to me — I won’t own them, or the ground they are planted in.
For me, there are two issues with walled gardens. Firstly, and most importantly, the owners of these networks tend to try and force people to sign up to their networks — I can’t see what someone has posted on Facebook, for example, without first signing up to Facebook. The second issue is one of exportability — once you have placed your content into the walled garden it can be difficult, if not impossible, to get it back out.
In the case of WordPress, neither of these issues apply. You don’t need a WordPress account to visit, or follow, this blog and if I do decide to self-host again at some point in the future, exporting and importing my posts is a very straightforward process.
Crucially, I do own this domain name and, if I did decide I wanted to self-host again, it would be possible to do so pretty much seamlessly. And because I can easily move the blog, I have much less desire to do so.
And by hosting the blog on WordPress, I can leave tasks like security, sizing and the rest to people who (should) know what they are doing.
WordPress may be a bit of a walled garden, but the walls are very low and the gates are wide open.