Fiat Lux

I’m settled in at the new web host now — who by the way, is A2 Hosting, and no, there’s no referral link on that URL.

So far it’s been great. The blog and the assorted other web files are all in place. I’ve cleaned out some old stuff I don’t need to keep on the server anymore. I’ve updated my robots.txt to reflect the new site layout. I have IMAP set up on my desktop and my laptop. Everything is running smoothly, DNS seems to have transitioned, and all is right with the world.

I’m even taking advantage of the fact that my new account has more bells & whistles to set up a side blog for recipies. It’s not quite done yet but when it is I’ll post a link.

What’s amazing is how much easier all this has been. When I first set up a website in 1996, this was very much a manual process, and you needed to either have direct access to the server and/or be very comfortable with a command line do stuff like set up a domain name, create a new web hosting account, or customize a website. Today, it’s nearly all web-based and so very painless. I love it. YAY for progress!

I decided to give a new web host a try, and am in the process of switching servers. The site may be a bit flaky over the next 48-72 hours as the DNS changes propagate.

UPDATE: Testing the new site….

UPDATE #2: Looks like everything’s set. All in all, I’m really pleased with myself. I hit a few glitches, mostly related to file permissions and pathing, but I’ve gotten the blog, e-mail, file dump and archives all moved.

Please let me know if you find any broken stuff!

In 5 days, I’ll either need to be set up and running on a new webhost, or I’ll have to fork over the money to my current webhost for another year of hosting services.

It’s been a little busy lately, and I don’t really have the bandwidth to get set up on a new webhost. And frankly, although my current host can be a little slow when it comes to server response times, by and large I’ve been satisfied with the service this year.

Still, it would be nice to have an IMAP server for my email. And faster web server response would be good, too. Maybe an easier to use control panel.

I’ve gotten feedback from friends, and searched the web for reviews, and I do have one hosting company bookmarked. I might pull the trigger and switch. But right now the odds are high that come Oct 30 I’ll still be parked right where I am.

You might notice that the blog looks a bit different tonight.

Scott decided that it would be fun to go to the WordPress Upgrade Party that the inimitable Matt M held Wednesday night. I figured, it was a good time to see if I actually could port the blog over from Movable Type to WordPress. With 1220+ entries in the database, I was more than a little worried that trying to move them all would be hell and result in me having one massively screwed-up blog.

Well, I was wrong. The process was unbelievable pain free. Absolutely everything just worked. Amazing. I’m so used to tech stuff almost-but-not-quite working; for something to NOT screw up or require weird hacking to get it right felt…. wrong.

At any rate, I got the data ported over last night; tonight was the fun stuff. Find a theme, customize the sidebar, add a few plug-ins. The move is about 98% done, but if you catch any weirdness or bad links, please let me know. I still need to re-add the comment policy and a link to my old travel blog, plus decide what kind of spam filtering I’ll be doing. Akismet is up and running, but that may or may not be enough.

So…. after 4+ years, it’s farewell to Movable Type. I feel a little sad about it, but it’s time for a change.

Like it? Hate it? Let me know!

So, a few weeks ago, I was getting fed up with the comment spam onslaught, and tried using captcha technology to shut it down. And it worked, which was great, but it also caused some problems for some readers, which was not so great. Pissing off readers is not something I want to do, so I dropped the captcha and am trying some new back-end spam filters instead.

Although the new spam filters seem to be working well so far, I’m a bit bummed about the outcome, because the captcha plug-in I was using — reCaptcha — is a bit more than your average spam deflector:

ReCaptcha is a rather clever service using them to help digitize books scanned into the Internet Archive as well. It’s a project from the School of Computer Science at Carnegie Mellon.

The Internet Archive is home to over 200,000 scanned copies of classic books. Some of them are gorgeously crafted, like this children’s book, but fancy styling can make it difficult for computers to translate the books into an indexable digital text. Much like a Mechanical Turk application, ReCaptcha uses humans to translate images of scanned words that a computer couldn’t understand.

I’d like to implement ReCaptcha at work instead of the captcha currently in place on the blog there, but it’s busy as hell right now; I probably won’t be able to get to it for a few more weeks.

Four years ago today, Fiat Lux came online.

I’ve averaged a post every 1.21 days since then. Not bad, for a solo effort (plus one guess post from Scott).

I’ve had days where fewer than a dozen people came to my site, and a few days where more than 6,000 people stopped by.

I’ve had days where I couldn’t wait to get something up onto the blog, and days where I’ve though about shutting it down entirely.

I’ve learned a lot about the mechanics of web marketing — SEO, how to build traffic, how to get links — that I use in my professional work.

I like to think that the discipline of writing this blog has made me a better writer (although this post is probably not one of me better efforts in that regard). At the very least, I’m more aware of my weaknesses as a writer now, and hopefully I do a better job of working through them.

Lately, though, it feels like most of what I want to write about is me, me, me. And this blog is at it’s best when it’s not all about me. Not sure how to resolve that contradiction right now; perhaps I need a few more days away from the blog to get my groove back.

I closed my first post like this:

What next? Who knows. But I think that I’d like to blog the journey.

And now, 4 years later, I still do. So let’s see what happens.

I’m of the camp that feels a blog is not a blog without comments. I also feel that there should be as few barriers to entry as possible when it comes to allowing comments. Easy interaction is a huge part of what has made the Internet great, and I’m a huge fan of it.

However, the damned comment spammers have made it impossible for me to run my blog the way I’d prefer. The vast majority of my older blog entries have had their comments closed to keep the spammers at bay, I’ve added all sorts of anti-spam plug-ins, and I’ve turned trackbacks off entirely.

And despite it all, especially in the last 48 hours, the comment spam has been overwhelming.

So today, and unwillingly, Captcha verification has been added to the blog comment form (Thanks Scott!). I really wish I didn’t have to, but it’s either that or go to some form of user registration / comment moderation, and on balance, I think Captcha is a little less of a burden all around.

To all you comment spammers out there who’ve forced me into this: You suck.

To the rest of you: I’m sorry. I hope it’s not too much of a hassle.

A month or so ago, I posted a blog entry noting that I was having a problem with comments vanishing when I posted to Wordpress blogs. Thanks to the kind operator the Burbed blog, who listened to my complaints and took the time to do some testing, I finally have an answer to why my comments were vanishing into the aethir.

Apparently, my ‘handle’ of Fiat Lux is classed as ‘definitely spam’ by one of the common Wordpress spam filters (presumably Akismet).

That’s moderately annoying, since I’m rather fond of that phrase.

So in the wake of the Kathy Sierra situation, Tim O’Reilly has created a draft of a Blogger’s Code of Conduct.

Frankly, I don’t see why deciding to moderate one’s comments is such a big deal. We all do it already in order to mitigate spam; this is not all that different. It doesn’t need badges and it doesn’t need a long, painfully worded Code.

Here’s mine, from December 2005:

I reserve the right to remove any comment left on this site, for any reason or for no reason at all. I pay for the web hosting; I get to decide how my disk space and bandwidth are used. However, I do not edit comments; that seems unfair. If they do not get tossed into the bit bucket, they remain as their authors wrote them.

I see no need to change that policy. I support the rights of free, anonymous, and/or pseudonymous speech online. However, that doesn’t give you the right to say something I don’t like on my dime. Don’t like it? Go over to Blogger or Vox or Wordpress and get your own site. Problem solved.

UPDATE 1:50 PM:

Tony Hung gets it absolutely right:

Bloggers don’t need a code of conduct, because it isn’t the content of blogs that are in the question. What’s being called into question is the cowardly personal attacks that are sent by email, and left in the comments sections of blogs.

And if that’s really the issue, then calling for a Bloggers Code of Conduct is pointless.

I decided that I have too much else to get done before I head out for Europe to deal with finding a new web host this month.

However, MT-Blacklist is still hosed and at this point I don’t believe that Powweb is either willing or able to help me fix it. So until I have the time to really deal with this issue, I’ve turned off all trackbacks on the site and I am going to be very aggressive about turning off comments after a couple of days. I don’t like doing this, but there’s no other way to keep the blog spam under control for now.