Oops! Subscriber Feed Accidentally Turned Off

I accidentally turn off the subscription feature, halting the notifications about new posts.

I should have known I’d done this because I also did it on my Great Loop blog. I turned off a plug in back in April and that inadvertently turned off the blog subscription feature — except, apparently, for WordPress.com account holders. I’ve since fixed the problem. If you’re a blog subscriber who used the form in the sidebar to sign up, here are the posts you may have missed:

There aren’t many of them because, frankly, I’ve been enjoying life too much to stop and write about it. (Have I mentioned anywhere how awesome retirement is? I should blog about that.) What I do write these days has been mostly in my Great Loop blog.

Battling Comment Spam

An interesting — but unfortunate — statistic from this site.

One of the biggest challenges to bloggers who allow comments on their blogs — other than dealing with immature, know-it-all asses who can’t write a civil sentence — is comment spam. It generally comes from three sources:

  • Automated spambots that are programmed to post comments on blogs. This accounts for more than 90% of the comment spam out there.
  • Real people who manually post comments that promote their products, services, or websites.
  • Pingbacks from blogs built by scraping content from other blogs, primarily to attract hits to other links on their pages.

I wrote about comment spam extensively on my Maria’s Guides site when I was regularly providing fresh content about WordPress. If you’re a blogger, you might find the following posts there interesting:

Spam vs. Ham on An Eclectic MindWordPress’s anti-spam tool, Akismet, does an excellent job of catching and filtering out spam so I don’t really need to see it at all. It also provides statistics about comments. This morning, while looking at these stats, I discovered that a full 98% of all comments posted on this blog are spam — or about 4,000 to 10,000 spam comments a month — leaving only 2% as legitimate comments (or “ham,” a term used by Akismet).

If this percentage is about the same on all blogs, it’s easy to see why so many bloggers elect to either turn the commenting feature off or require registration for commenting. (Note that registration doesn’t always help; some spambots can also register an account and then manual intervention is required to identify and delete those accounts.)

Comments are moderated here for two reasons:

  • Aksimet doesn’t catch all spam. It misses, on average, about 10 spam comments a month.
  • Akismet can’t identify abusive comments.

I have a zero tolerance approach to spam and abusive commenters and don’t want to see any of it on this blog. So I manually review all the comments that Akismet approves before allowing them to appear on this blog.

June 30, 2014 Update
I’ve finally gotten around to writing up the site comment policy on a regular page (rather than post) on this site. You can find it here: Comment Policy.

(If you believe that deleting comments is censorship or somehow violates your freedom of speech, read this and this.)

Personally, I’d like to see a higher percentage (and number) of legitimate comments on this blog. I like when good conversations get going among readers. I can think of two posts offhand where reader comments have added real value to what I’ve written: “The Helicopter Job Market” and “Why Groupon is Bad for Business…and Consumers.” I write from experience and my experiences are limited. When readers share their own thoughts based on their experiences, they provide more information for other readers to draw upon. They help round out a discussion. And as long as they don’t get rude or abusive to me or other commenters — or are obviously commenting to promote their own product or service (i.e., spamming) — I don’t care if they disagree. Intelligent, civil debate based on facts is encouraged.

But while comment spam is obviously a serious problem for all bloggers that allow comments on their blogs, I have it well under control here.

Web Site Redesign: Fitting in My Photos

With 90+ photos appearing randomly in my old site’s header, I wasn’t about to leave them behind.

CutlineOne of the reasons I chose the Cutline 3 Column Right theme for my site’s redesign is because I wanted a three column layout that was wider than my old site. Studies — including stats from all of the sites/blogs I operate — showed that the vast majority of Web site visitors have their screen resolutions set to 1024×768 or wider. I even use that setting on my little 12″ PowerBook. So the old site’s redesign was throwing away 200+ pixels of screen real estate that could be better used providing content or navigation features.

How Do I Use Those Images?

The problem I faced was the header image. Since I built my blog in WordPress nearly two years ago, I had been displaying images that I’d taken during my travels. The images had to be cropped and fit into pre-established format. I used the Random Header plugin to randomize the display. Over 18 months, I’d added nearly 100 images to the header image collection. I’d even begun writing about them in the About the Photos topic. They had become an integral part of my site and I didn’t want to lose them.

So while I continued working on my Leopard book during the day, this little problem was in the back of my mind. For days. One option was to rework the CSS and change the header image so it only took up a portion of the width and use the space beside it for a Web site description. Unfortunately, I don’t know enough CSS to do this successfully without spending hours on trial and error. With a deadline approaching, I couldn’t afford to waste time experimenting. I had to have an answer and be ready to implement it.

About the Photos Images

Then I remembered the smaller images I use in About the Photos to show the images I’m discussing. What if I put three of them side by side and displayed them with some sort of randomizer? Would they fit? What would they look like?

Example ImageThe images in question were 324 pixels wide. The space I had to work with was 970 pixels. 3 x 324 = 972. My luck, sometimes.

I reduced the size of three images to 322 wide and began some quick experiments to replace the existing header image (the street scene you see in the screenshot above) with the three images. I could get them to fit and they didn’t look bad. But I couldn’t get the spacing between them just righ. And I didn’t like the way they fit right up against each other.

A Short Film History Lesson

Then I came up with the film sprocket idea.

For those of you who began using a camera in the digital age and aren’t familiar with 35mm film, let me explain. Before everyone started using digital cameras, serious photographers used 35mm film. The film comes on rolls and has tiny holes along each side. A camera has gears that line up with the holes. You feed the film into the camera and it grabs the holes with its gears. A mechanical lever pulls the next blank piece of film from the film canister to the place in front of the shutter for the next photo. When the roll was finished, the photographer (or his camera) would roll the film back into the canister and the photographer would drop it off for processing. When he picked it up, he’d get prints and negatives. The negatives are the actual film, with inverse (or negative) images on them.

If a photographer had his own darkroom, he’d likely make a contact sheet. This was created by putting the negatives right against a sheet of photographic paper in the dark, then exposing the paper to light for a short time and developing it. The resulting images were tiny (at least they were from 35mm film) and clearly displayed rows of black boxes on either side of the image with black lines between them — like you see here in the header of my redesigned site.

So anyone who has worked with film should recognize these little holes. Of course, my images are considerably larger and wider, so they’re not exact representations of contact strip images. They’re just borrowing the idea.

When I modified the three images to include the borders and fake sprocket holes, I liked what I saw. I created a Photoshop action to modify the 89 remaining images so they were smaller and included the tiny black boxes and borders.

Randomizing

On my old site, the random header image was randomized with a WordPress plugin named Random Header. But since I had three images to show in my header, I needed a different solution. So I turned to the software I used on Flying M Air’s Web site to randomize some of the images there: Random File.

Random File enables you to display random files anywhere on a template. (If you use a plugin like Exec-PHP, you can even display them within posts.) What’s neat about it is that you can tell it how many random files — well, in my case, images — to display and it will display that quantity without repeating them.

After some fiddling around with the CSS used in header.php — remember, I’m no expert — I added the following code in place of the existing header image code:

< ?php $files = array(); for ($i=1;$i<=3;$i++) { $file = c2c_random_file('/wp-content/foldername/foldername/', 'jpg png gif', 'url', $files);
echo 'Random image #' . $i . '';
$files[] = $file;
}
?>

The result is what you see here.

The Hard Part Was Done

With the tough design decision done, I was ready to put the new theme into place. I did that on Saturday, taking most of the day to get it 90% functional. I’m pleased with the results.

Comments? Questions? Use the Comments link or form for this post.

January 3, 2009 Update: I’ve since updated my site’s Web design again and adopted a new theme that does not include photos in the header. So although this information may still be useful to WordPress users, there’s no live example for you to see what it looks like. Sorry.