Althouse is having problems with the new Blogger. The “new and improved”, post-upgrade software seems to be as palatable as New Coke. She describes the issues from the blogger’s perspective and I can attest her site is taking a while to load. Haven’t tried to post any comments yet. I noticed similar problems with Gateway Pundit’s site a month or so ago when he was upgrading to the new Blogger. Gateway Pundit’s site always took longer to load, but for several weeks it took a really long time. Seems to be back to normal slow speed now so perhaps the Althouse issues, at least for the visitors, will resolve over time.
I had looked at Blogger several years ago and didn’t much care for the interface and functional layout from a blogger’s perspective. The steps for posting comments still strikes me as rather tedious. I have some doubts about how Blogger tracks web traffic, too. Over the past several months I’ve been working to sort out the JZ:TOL traffic patterns and the trends have been rather interesting. SPAM has been the biggest issue. As I identify IP addresses associated with SPAM, I ban them and they drop out of my traffic statistics. Bots are another big issue. In most cases, I want the bots because I want my blog to show up in search engines and such. But I don’t include bot traffic in my stats. Does Blogger count SPAM hits, even ones that are successfully filtered? Does Blogger count bot scans as if they were visitors? Same questions could be asked of the various third party site meter services.
Eventually, I settled on WordPress and have used it ever since. But there was a deeper criteria for me when looking for a content management system. I had to have complete control over the system. I wanted unfettered access to the web logs, the database, the code and the system. This means it had to be hosted on a machine I owned. This greatly expanded the options for software, backup and recovery strategies, and upgrades.
Granted, the capability to manage such a system is extra work and not something that is desirable for the vast majority of bloggers. It’s a question of trade-offs and accumulated experience. System administration tasks are for me what handling a saw is for a woodworker – not much effort because of the many years practice in handling the tools. Upgrades to JZ:TOL always occur on a non-public mirror site so I can see the effect and assess the impact of any upgrades or code changes. The upside is near transparent upgrades to the public blog. And in the unlikely event of a water landing after an upgrade to the public blog, I have a rollback strategy in place that can restore the previous site in a matter of minutes. Apparently, Blogger doesn’t have such capabilities. Having such a system in place also makes the blog more secure as patches and upgrades can be tested and pushed within hours of the announced patch or upgrade.
Like I said, it’s a question of trade-offs and accumulated experience. When I have a legal problem, even a relatively small one, I hire an attorney. With Althouse, probably not the case.
Didn’t mean to imply JZ:TOL is hosted on WordPress. Rather, I use the WordPress software application on my own javazen.com server. Ambiguity fixed.