For close to a decade, since October 2000, I've published this home page using Blogger, the online publishing platform now owned by Google. That entire time, I've used the original hacky kludge created by Blogger's founders back in 1999, where I write my posts at the blogger.com website, but it then sends the resulting text files over the Internet to a web server I rent, using the venerable FTP (File Transfer Protocol) standard—which was itself last formally updated in 1985. This is known as Blogger FTP publishing.
While often unreliable for various technical reasons, Blogger FTP works effectively for me, with my 13 years of accumulated stuff on this website. But I am in a small, small minority of Blogger users (under 0.5%, says Google). Almost everyone now:
So, as I've been expecting for years, Blogger is now permanently turning off FTP publishing, as of late March 2010. And, in my particular case, that means I need to find a new blog publishing tool within the next month or so.
Blogger has all sorts of clever solutions and resources for people using FTP publishing who want to migrate to Google's more modern server infrastructure, but they don't fit for me. I have specific and very personal needs and weird proclivities about how I want to run this website, and putting my blog on Google's servers simply doesn't meet them.
That's sad, and a little frustrating, but I'm not angry about it—and I think it's misguided that many people commenting on this topic seem to be. I realize that I have been getting an amazing, easy publishing service for free for almost a quarter of my life from Blogger. It has enriched my interactions with thousands of people. Again, for free. (Actually, I did pay for Blogger Pro back in the day before the 2003 Google acquisition, but that was brief. And as thanks, Google sent me a free Blogger hoodie afterwards—I still wear that.)
The vast, vast, vast majority of users find the newer ways of publishing with Blogger meet their needs. And any of us who has used FTP publishing for years knows it's flaky and convoluted and something of a pain in the butt, and always has been since Ev and his team cobbled it together. I've been happily surprised that Blogger has supported it for so long—again, free.
Yes, it was a distinguishing feature of Blogger that you could use a fully hosted editing and publishing system to post to a web server where you don't have to install anything yourself. Very nice, but I think there are good technical reasons that no other service, free or paid—whether WordPress.com, TypePad, SquareSpace, or anything else—ever offered something similar.
I applaud the Blogger team for trying to do the best they can for us oddballs. And it serves as a reminder: Blogger FTP can go away. Gmail could go away. Facebook could go away. Flickr could go away. Twitter could go away. WordPress.com could go away. If you're building your life or business around free online tools, you need some sort of Plan B.
I've had this possibility on my mind at least since the Google takeover, seven years ago. Now I have to act on it. But I'm thankful for a decade of generally great and reliable free service from Blogger. I haven't had ten free years of anything like it from any other company (online or in the real world), as far as I know.
One other thing I've always liked about Blogger's FTP publishing is that it creates static files: plain-text files (with file extensions like .html or .php or .css, or even no extensions at all). It generates those files from a database on Google's servers, but once they're published to my website, they're just text, which web browsers interpret as HTML (Hypertext Markup Language) to create the formatting and colours as such.
Most other blogging tools, including Blogger's hosted services, generate their web pages on the fly from a database. That's often more convenient for a whole bunch of reasons, and I'm happy to run other sites, such as Inside Home Recording and Lip Gloss and Laptops, with a database-dependent tool such as WordPress.
But this site is my personal one—the archive of most of my writing over the past 25% of my life. And I'm a writer and editor by trade. This website is my thing, and I've worked fairly hard to keep it alive and functional, without breaking incoming links from other sites, for well over a decade now. I've always wanted to keep it running with static files, which is one reason I didn't migrate from Blogger to WordPress four or five years ago. Over on Facebook, Gillian asked me why I'm so hardheaded about it. (She's a database administrator by trade.)
I'll be blunt about the most extreme case: I have cancer. I may not live that long. But I'd like my website to stay, even if only so my kids can look at it later. If necessary, if I'm dead, I want someone to be able to zip up the directory structure of my blog, move it to a new server, unzip it, and there it is, live on the Web. I don't want to have to plan for future database administration in my will.
In that worst case I won't need to update my site anymore, but I think static files on a generic web server are more reliable in the long run. To make a bulk change, a simple search-and-replace can update the text files, for example, to note that it's not worth emailing me, since, being dead, I'll be unable to answer.
On other blogging and content management systems I've worked with, I've had MySQL databases die or get corrupted. Restoring from MySQL backups is a pain for non-techies, or even for me. I've blown up a WordPress site by mis-editing one part of one file, and I've been able to fix it—but I don't want someone else to have to do that.
Right now, if Blogger died entirely, my site would still work exactly as-is. If my web host went belly-up, anyone with a teeny bit of web savvy and access to my passwords and one of my computers could redirect penmachine.com to a new server, upload the contents of one of my backup directories to it by FTP, and (other than visitors being able to post new comments) it would be up and live just like it was within a day or two.
In addition, tools like WordPress are brittle. I like using them, but there are security updates all the time, so the software goes out of date. That's fine if you're maintaining your site all the time, but if not, it becomes vulnerable to hacks. So if a database-driven site choogles on without updates, it's liable to get compromised, and be defaced or destroyed. That's less likely with a bunch of HTML files in directories—or at least I think so.
Plain text has been the language of computer interchange for decades. If the Web ever stops supporting plain text files containing HTML, we'll all have big problems. But I don't think that will happen. The first web page ever made still works, and I hope and expect it will continue to. My oldest pages here are mild derivatives from pages that are only five years younger than that one. They still work, and I hope and expect that they will continue to.
At worst, even a relatively non-technical person can take a directory dump backup of my current website and open the pages in a text editor. I can do that with files I've had since before the Web existed—I still have copies on my hard drive of nonsensical stories from BBSes I posted to in the '80s (here's an HTML conversion I made of one of them). I wrote those stories with my friends, some of whom are now dead, but I can still read what we wrote together.
Those old text files, copies of words I wrote before some of the readers of this blog were born, still work, and I hope and expect they will continue to. Yeah, maybe a SQL backup would be wise, but I'll still place my bets on plain text. Okay, I'm weird, but there you go.
Okay, so I need a new blogging platform. Probably one I can install on my server, but definitely one that generates static files that don't depend on a live database. Movable Type does that. ExpressionEngine might. More obscure options, like Bloxsom and nanoc, do so in slightly more obscure ways.