Tag Archives: books

Tumblelogs

Posted on by
Comment

I discover a new, abbreviated form of blogging.

One of the things I’ve noticed about my blog is that a high percentage of the entries are extremely wordy, full of stories or opinions or information that I’ve spent a lot of time thinking about, compiling, formatting, and publishing. And it seems that most serious blogs are the same.

Enter, the tumblelog, which has apparently been around since 2005. This short-form blog is ideal for quick and dirty entry posting. In fact, that’s what it’s supposed to be for.

From Wikipedia:

A tumblelog is a variation of a blog, that favors short-form, mixed-media posts over the longer editorial posts frequently associated with blogging. Common post formats found on tumblelogs include links, photos, quotes, dialogues, and video. Unlike blogs, this format is frequently used to share the author’s creations, discoveries, or experiences without providing a commentary.

I first heard of tumblelogs on either the TWIT or MacBreak Weekly podcast. Leo Laporte and other members of those two podcast teams use Tumblr to create and publish their tumblelogs. Curious, I went to check it out for myself. And, on the FAQs page there, I got a the analogy that sold me on trying it for myself:

If blogs are journals, tumblelogs are scrapbooks.

It might be nice to have an online scrapbook, I thought. I decided to sign up for a free Tumblr account and give it a try. The result is the unimaginatively named Maria’s TumbleLog, which can be found at tumblelog.aneclecticmind.com. (And yes, you can host a tumblelog on Tumblr’s site; I just got fancy and set mine up with my own custom domain name.) Since then, I’ve added entries that include photos and quotes. I’ve also set up my account to automatically create links to new articles in a number of feeds — including the one for this WebLog.

Although I like the ease at which entries can be added to my tumblelog, I don’t like the fact that there’s no offline composition tool. But I think that’s because I’m worried about composition — a task that simply doesn’t apply to tumblelog entries. Entries are extremely short and to the point: a photo with a caption, a quote with the name of the person being quoted, a link all by itself. While it is possible to create a standard text entry, I’m going to try hard not to — unless I can keep it to 100 words or less. That’s not an easy task for me — writing more has always been easier than writing less.

Will anyone read my tumblelog? I don’t know. Do I care? I don’t know that, either.

Right now, the idea is too new to me. I’m more interested in experimenting with this form of expression and seeing whether I can stick to it.

I’ve been blogging for 3-1/2 years now; it’ll be tough to branch some of that energy off to a similar yet very different form.

In the meantime, I’d be very interested in hearing from others with tumblelogs. Use the comments link. And be sure to include a link to your tumblelog in the form so other readers and I can check it out.

Death of a Manuscript

Posted on by
1

Dealing with the loss of my own unpublished words.

Last week, I discovered that a file containing the manuscript for a novel I was working on was gone.

The file lived in my laptop, which is what I was using to write it. It was backed up on my main computer’s hard disk. I had decided two or three months ago to keep working copies of all my fiction on my iDisk space. (iDisk is part of the .Mac services available for Macintosh users. It gives you 1 GB of storage space on an Apple server that can be shared among all of your computers.) The idea was that by keeping the files there, I could work on them from any computer and always have the most recent version.

Somewhere along the line, while copying the folder containing this file to my iDisk space, the file was lost. I’m not sure how it happened, but I do recall getting an error message when I made the copy. I should have investigated more closely, but I didn’t. The file was gone and because I didn’t work on it for months, I didn’t realize it was gone.

The backup copy, of course, was lost in my February hard disk crash.

I spent most of a day playing with file recovery software to get the file back. I managed to retrieve about 2 of the 97 pages I’d written.

Obviously, I’m not very happy about this. I’d been working on this project on and off for about four years. There was a lot of me in it. I’d written a lot of good dialog and some pretty strong scenes. It wasn’t perfect — the characterization on a few of the characters was just not good enough — but what was good was very good. A lot of “keeper” stuff in there.

And now its gone.

I find the task of recreating this work daunting. Lately, I just don’t feel that I have the writing skills I need to write fiction. I have my outline, my index cards for scenes, my character notes. I can clearly remember lots of the scenes and even some of the dialog. But I don’t feel confident that I can rewrite what I lost. I know that when it comes time to sit down and type it all back into my word processor, there will be something lacking. It just won’t be as good or as complete.

Fortunately, this was the only manuscript I lost (other than the partially completed Chapter 6 of my Excel for Windows book, which was easy, if not tedious, to recreate). My other fiction manuscripts remain safe, now backed up to three places. But although I’ve been toying with them for far longer — one of them originates back in my teenage years when I wrote longhand in spiral bound, college ruled notebooks — the loss of this one seems to hurt more. It was a more mature work, a more marketable work. It, unlike my other fiction scribbling, had a future, possibly in print.

Time is now my main obstacle to picking up this work and recreating it. I’m juggling two jobs: as a technical writer and a helicopter pilot. I’m having a hard enough time getting both of those jobs done. At the end of a working day, I’m mentally exhausted and not prepared to tackle a recreational writing assignment. (That’s one of the reasons I do 90% of my blogging first thing in the morning.) So who knows when this work might be resurrected?

Perhaps it’s something to look forward to in my retirement years.

Using Google AdSense Channels

Posted on by
1

Article now available on Informit.com.

My latest Informit.com article, “Using Google AdSense Channels” is now online.

From the article’s intro (written by editors, not me):

Google’s AdSense program is a very popular advertising option for blogs and web sites because it’s easy to use and can generate revenue with minimal effort. Maria Langer explains how to use the Channels features in AdSense to track which of your ads are earning the most revenue.

This article should be of special interest to bloggers and traditional Web site webmasters who try to raise revenue using the Google AdSense products.

There are two other Informit articles in the pipeline. Keep checking in; I’ll let you know when they’re released. Or check my Informit.com books and articles page for yourself to see what’s new.

Being a Responsible Blogger

Posted on by
2

With regular readers comes responsibility.

This morning, I noted that the feed for this blog has exceeded 100 subscribers. The 100 mark is a milestone for any blogger, and it’s no different for me — even though I’ve been at it for some time now.

I’ve been blogging for over three years and my blog doesn’t exactly follow all of the “rules” of blogging. I’m talking about the “stick to one topic” rule and “blog multiple times a day” rule. People say rules are meant to be broken, but that’s not why I break these rules. I just blog the way I want to blog and don’t really pay attention to the rules.

My Original Blog as a Separate Entity

My blog started out as a separate entity from my personal Web site, a way to share whatever I was thinking about or doing with people who might be interested. It was a personal journal, slightly filtered for the public. It was a way for me to record my life so I’d have something to look back on in the distant future. I didn’t care if anyone read it and was often surprised when someone I knew commented about something I’d written in my blog.

Back in those days, my blog wasn’t something I worked hard at; the entries just came out of me, like one-sided conversations with friends. Perhaps it has something to do with my solitary work habits — many people gather around the “water cooler” at work to trade stories about their weekends or opinions about world affairs. There’s no water cooler in my office and no co-workers to chat with. My blog may have been my outlet for all these pent-up stories.

Blog + Site = ?

A little over a year ago, I combined my blog with my personal Web site. I did it to make my life a little easier. I’d already decided to use WordPress as my Web site building tool. Why not just make my personal blog part of the site?

My Web site has been around in one form or another since 1994. I built it to experiment with Web publishing and soon expanded it to provide a sort of online résumé and support for my books. Support for my books often meant additional tips and longer articles about some of the software I’ve written about. This is fresh content of interest to people who use that software, even if they don’t buy or read my corresponding books. Since writing this content is relatively easy for me, I have no problem offering it free to anyone who wants it (as long as they don’t steal it and pass it off as their own; see my © page).

One of the great things about blogging software is that it automatically displays the newest content on the Home page and archives older content by category and date. In the old days, I’d have to manually create new pages for every article I wanted to put on my Web site and then add links to them. It was time consuming, to say the least. Sometimes too time consuming to share even the quickest little tip with visitors. So I didn’t publish very many articles. But the time-consuming, hand-coding aspect of my site is gone, and it takes just minutes to put any content online, whether it’s a link to an interesting podcast I just listened to about iPod microphones or a multi-part series of articles explaining how to use WordPress as a content management system.

What’s odd about the merging of the two sites is that my personal blog entries now commingle on the Home page with my book support entries. So these 100+ subscribers are seeing (and possibly reading) all kinds of stuff coming out of my head. (Now that’s a scary thought!)

My Responsibility

As my blog/site audience grows, my responsibility to provide good content for readers also grows.

The way I see it, when only a half-dozen people read my blog regularly, it was okay to bore them with stories about my horse eating corn cob stuff out of the bottom of my bird’s cage or rants about the quality of “news” coverage. Now, with over 100 regular readers, I need to think more about what would interest my audience and concentrate on producing the articles they want to read. (You can help me by voting on this poll.)

And that’s when blogging becomes work. That isn’t necessarily a bad thing, but it does take more effort on my part.

And it may push me far from the original purpose of my blog: a journal of my life. That’s something to think about, too.

The Other Blogs

I just want to take a moment here to comment on some of the other blogs I’ve seen out there. The vast majority of them are a complete waste of bandwidth. Some exist to echo the sentiments of others and show very little original thought. Others are complete blather, written in a style that makes me mourn for the failure of our educational system. Like chat room comments. Ugh. I don’t see why people waste their time writing this crap and really can’t see why people waste their time reading it.

But there is a small percentage of blogs that provide good, informative, or at least interesting content, written in a way that’s easy to read and understand. Those are the blogs that serious bloggers should be reading and learning from. Those are the blogs we should try to emulate, not by simply copying or linking to content, but by adding our own original material to the blogoshere.

That’s my goal and my responsibility as a blogger. If you’re a blogger, is it yours, too?

Web Site vs. Blog

Posted on by
10

What’s the Difference?

Today I got a phone call from our local newspaper’s “business advocate” — the guy who writes stories about business. He was researching an article about blogging and figured that I was the most active blogger — if not the only blogger — in town, so I might be able to to provide some information about it. He wasn’t aware that I’d co-authored a book about WordPress blogging software (WordPress 2: Visual QuickStart Guide) in 2006 and he probably wasn’t aware that I wrote Putting Your Small Business on the Web back in 2000. He probably also doesn’t know that I’ve written four books about Web authoring software (various versions of PageMill, now defunct) and that I’ve been building and managing Web sites since 1994 (although I’m not crazy enough to do it for a living).

We stumbled a bit in our conversation. He referred to my Web site, wickenburg-az.com, as a blog. (The site has been around since 1999, predating the blogging phenomena by at least 3 to 4 years.) I responded that it wasn’t a blog, that it was a Web site built with blogging software. And then he asked me what the difference was.

I had to think about it. What is the difference between a Web site and a blog?

They’re very much alike.

Let’s take a look at the similarities.

  • Web sites and blogs are both published on the Web and can be read with any Web browser. This gives them the same basic look and feel and similar user experiences. Web sites built with blogging software can look and feel just like a blog, even if that’s not what they are intended to be.
  • They depend on good, useful content. Web site visitors and blog readers come to read content. If the content is good and meets their needs, they’ll be back for more. If the content sucks, they won’t.

But they are different.

Of course, I needed to explain how they were different — not how they were the same. The response I came up with centered around the purpose of visitors coming to to the site, but there are more differences.

  • Web site visitors come to a site to look for specific information. That information does not need to be new. It just needs to be what the visitor is looking for. For example, I visit the HP Web site when I need a new driver for one of my printers. I know it’ll be there and I don’t care if it’s been there for five years. People visit wickenburg-az.com to get basic information about Wickenburg: what it’s like, what to do there, etc. But blog readers visit or subscribe to blogs to get fresh information or insight on topics that are important to them. I read ProBlogger, for example, because it has timely articles that can help me understand how to be a better blogger. People visit aneclecticmind.com to read articles like this one about blogging, or other articles about flying, or even other articles about what it’s like to live in a place like Wickenburg — all from my point of view.
  • Blogs tend to be more opinion-based than Web sites. Sure, HP is going to tell you on their Web site that their printers are the best, but what would you expect? On my blog, I’ll tell you what I think about my HP printer and compare it to other printers I might own or have experience with. I’ll also tell you what I think of Apple Geniuses or local restaurants or life revolving around the Internet. (Although some locals might find this hard to believe, I keep most of my negative opinions of Wickenburg out of wickenburg-az.com. Most.) The opinion aspect makes blogs more personal than a Web site.
  • Blogs rely on fresh content. It’s commonly accepted that a blogger should post at least 3 to 5 new entries a week. Web sites, on the other hand, are more static and don’t require as much updating. Their visitors don’t expect it, either.

Does it matter?

Who knows? But it’s made me think about blogging a bit more than usual lately. And I’m sure it will lead to a few more articles here about what makes a blog a blog in the near future.