An interesting podcast that describes me as a blogger.
There has been a lot — probably too much — said about blogging and bloggers. This Future Tense podcast, which can be found in the Future Tense: July 2006 Archives gets to the heart of the matter. (On that page, search for “Profile of Bloggers.”)
If you’re looking for a good podcast with short episodes about technology issues, I highly recommend Future Tense.
blogging, blogs, podcast
Stats can tell you a lot of interesting things.
I spent most of this morning updating the daily podcasts for KBSZ-AM, the local radio station.
KBSZ‘s Around the Town broadcast was my first foray into the world of podcasting. I wanted to experiment with the new technology but didn’t have any content available to experiment with. KBSZ was already doing a daily radio show. Why not podcast that?
Well, what started out as a fun and education project has become a bit of a chore. It isn’t difficult to turn their broadcasts into podcasts — especially since I also do streaming audio for them and my computer automatically records each show for me — but it is time consuming. You see, I can be a bit of a perfectionist at times. KBSZ’s show never starts exactly on time and never ends exactly on time. So there’s stuff at the beginning and end that needs to be edited out. Then I need to upload the podcasts files, create the podcast entries on their Blogger account, link the podcasts files, and publish. It takes about 15 minutes per episode. If I were smart, I’d just do it every day. But I’m not smart. I wait until there’s about 2 weeks worth and knock them all of at once. It took two hours this morning. Two hours that I should have been working on my WordPress book.
I do plan, however, to get very smart. I’ll skip the editing and fully automate the process. More on that when I find time to do it. Hopefully soon.
While I’m messing around with the podcasts, I often check the download stats for all podcasts and other files on my server. I serve all files from a GoDaddy.com hosting space. They give you a good amount of disk space and bandwidth for only $3.95/month — and even cheaper if you pay a year up front. So all podcasts and book support files live there. No need to bog down my limited bandwidth with visitor downloads.
Due to a server glitch, all stats prior to November 18, 2005 were lost. No big deal. I just started using that server seriously in August 2005. But it’s good to know the start date for the stats.
By looking at the stats, KBSZ can see who their most popular guests are. For a while, I was number 2 (behind the high school football coach — hey, sports are important here in Wickenburg). Now the top slots are held by the folks who make sure all their friends know about the podcasts. Some of the really smart ones link to the podcast from their own Web sites, further increasing the number of downloads.
While I was checking stats, I checked the stats for my own podcasts. I found that my video podcasts are among the most popular I do. That doens’t make me terribly happy, mostly because they’re a royal pain in the butt to create. Recording my voice reading a script is one thing, but inserting a bunch of screen shots at key points is another. Still, I’ll try to make folks happy by delivering a few more audio podcasts.
The excerpt from my Mac OS X Tiger book is by far the most downloaded file on my server. The Panther excerpt isn’t far behind. You can find both of those in the Mac OS QuickStart support area.
All this, of course, reminds me that I haven’t done a podcast in about two weeks. I’m behind already. Maybe I’ll throw something together on the plane to Austin on Wednesday.
Talk about junk e-mail!
Whew! I just unsubscribed myself to the last e-mail list I was subscribed to.
An e-mail list, if you’re not familiar with the term, is like a topic based mailbox that list subscribers can send messages to. When you send a message to the list, it’s automatically sent in e-mail to everyone on the list. The idea is that you can use a list to get information about a topic from people who might have answers.
The operative word here is “might.” A lot of times, subscribers won’t have an answer but they won’t hestitate to say “I don’t know the answer but wish I did” or “this might be the answer” or “that question is off-topic” or “you should ask that question in this other list, too” or “I just read the answer to that in this other list” or “why the hell do you want to know that?” Then the topic starts expanding in every direction, sprouting more questions and answers, only some of which are vaguely related to the original. Arguments develop with differences of opinion sometimes getting nasty. So one question can generate dozens of e-mail messages that may or may not have any value to the questioner. And if you didn’t ask the question in the first place and don’t care about the answer, it’s even more junk to wade through.
Of course, you can always take a list in “digest” format. That’s when they put a whole day’s worth of messages into one big, fat e-mail. I think it’s worse because you can’t even use a message’s subject line to determine whether it’s something you want to read (or delete).
One of the mail lists I was subscribed to didn’t have a specific topic. It was a strangely quiet list, with no messages for days on end. Once, I thought I’d unsubscribed to it — it was that dead. Then, suddenly, someone would send a message and twenty people would respond to it. Like they were all lurking out there, waiting for someone to make the first move so they could join in the fray.
The really weird thing to me is the amount of time that passes between the original message and the responses. Sometimes it’s as litle as a few minutes! Even in the middle of the night! Like people are sitting at their computer, watching every e-mail delivery, ready to dive in with a response when a message appears. Egads! Get a life!
Another list I belonged to briefly prevented me from posting questions or answers. Even though I was a subscriber, my messages were considered spam. Wow. Hard not to take that personally. I think I lasted about a week. Very frustrating when every time you try to chip in with a little assistance your message gets bounced back at you with a spammer accusation.
Why did I join these lists in the first place? Well, for a while I was feeling a bit isolated. I live in my own little world here in Wickenburg, one that’s very light on high-tech people. Very light. Lighter than the hot air the local “computer experts” spout while they’re pretending to their customers that they know what they’re talking about. I started feeling as if I were missing out on new developments in computer technology. That I lacked a reliable forum for getting answers to computer-related questions. That I had no place to turn to when I needed help.
I heard about a list from a friend and got mildly interested. When one of my editors praised it, I thought I was missing out on something really valuable. I jumped in. With both feet. And the barrage of e-mail began.
I’ve made worse mistakes. But not many lately.
So now I’m off the lists. All of them. My mailboxes are feeling much lighter these days.
I’m back to doing what I’ve been doing for the past few years. When I have a question, I hop on the Web and Google to get the answer.
A reader chastises me.
The other day, while writing about the Reading Options in WordPress, I decided to experiment with this blog. I togged the settings so only summaries of my entries would be sent to people accessing with RSS readers.
Understand that I don’t use an RSS reader. I surf the old fashioned way, with a Web browser. I don’t surf that often and I don’t follow any one particular blog or site. So it’s never been an issue for me.
But for the book, I had to understand what this WordPress feature did. So I toggled it to the Summaries setting, downloaded a feed reader, and looked at the result. What I saw was a list of 10 or so posts in a window. I’d click a post title and the beginning of the post would appear in a window pane beneath the list. There was a link at the end indicating that there was more; clicking the link brought me to my Web site.
This seemed a logical way to release content via RSS. After all, didn’t I want visitors to come to the site where they could read not just the articles but the comments? And see all the pictures that came with the piece?
Dori of Wise Women didn’t think so. She commented on my “Stand Up for Your Principles” piece to stand up for her principles: that RSS feeds for blogs should include the entire content.
Whew! No problem. This morning, I remembered what I did to create the summaries (I did have to remember something I learned about 2 whole days ago!) and toggled the option back to its original settings. I just checked it with my feed reader and it’s working fine.
But this makes me curious. I’d like to know more from the folks who use an RSS feed reader to follow this blog. Here are a few questions; I’d appreciate it if you’d take the time to answer a few of them in the Comments for this post.
Although I’m a technical person and write about computer technology for a living, I made a decision long ago to concentrate on only those technologies that I use or write about. There’s just too much out there to learn it all — and still have a life that doesn’t revolve around a computer! As a result, my knowledge of computer technology is spotty, with expertise on certain topics balanced by sheer ignorance of others. (Ignorance is bliss, they say.)
Perhaps its time to give the RSS feed reader topic a bit more attention. What do you think?
PostScript: I just used my RSS reader to check out the other blogs that were included in it. It appears that none of them include the full text of the article. What’s going on here? Perhaps that’s why I discarded the idea of using a reader when I first tried it about two years ago? Because you had to go to the Web site anyway to read the article? It seems that, in many instances, the reader adds an extra step to following blogs. If you’re commenting on this piece, please comment on that, too.
I find that there’s more to flying helicopters than giving tours.
Lately, I’ve been getting calls from folks who want to use my helicopter for more than just transportation or tourism.
The first good assignment I got came a few months ago, when I flew a camera crew around the a carmaker’s test track in Arizona. I wrote about it in another blog entry. This past week, I did two more.
The first, on Tuesday, was for a professional photographer hired to take aerial and ground photographs of the new bridge being built over Burro Creek on state route 93. There’s already a beautiful bridge there and the construction crew is building a twin on the north side of it (the road runs pretty much east-west there). Burro Creek runs in a deep canyon there and the Sonoran desert landscape is breathtaking. The site is also far from civilization — about 55 miles north of Wickenburg and perhaps 20 miles south of Wickiup.
It was a cold morning when we left Wickenburg, so I left the helicopter’s doors on. It took us about 30 minutes at my top cruise speed (110-115 knots with two on board and full fuel) to reach the site. I set down in a fenced-in area where the construction folks were storing cactus to be replanted after work was done. I took the passenger door off while my client got his camera equipment out — a pair of Hasselblad medium format cameras with three different lenses. A construction truck pulled up and my client got out to talk to the driver. He came back and told me that the next time I landed, I could land on the new road right near the bridge. It was closed to traffic and was smoothly paved. We took off and began circling the bridges from various altitudes. My client snapped away, cranking the camera’s advance do-dad after each shot. He was perfectly at ease leaning out the door; he’d flown in many helicopters before. After about ten of fifteen minutes of that, I set down on the road near the bridge and shut down. (I had to set down on the edge of the road, as shown in the photo below, because the road was banked for a curve and the only real level spot I could find was at the very edge of the road.) My client climbed out, filled a smaller camera bag with equipment, and walked off to take his ground shots.
I pulled out my iPod and a book and settled down on the side of the road to read. Cars and trucks drove by and I wondered how many of them were headed to or from Wickenburg.
He was gone about 90 minutes. When he returned and finished fiddling around with his equipment, we climbed back on board and I fired the helicopter back up. The light had changed, so we did another 10 or 15 minutes of circles around the bridge at all different altitudes. Then he told me to head back and I broke off circling and headed back.He took some more photos on the way back — using up extra film on shots he thought he might be able to sell the construction folks. Then we set down on Eric Barnes’s dirt strip, on route 93 near the Santa Maria River, so I could put the door back on. With the door off, it was loud and my speed was limited to 100 knots. With it on, it was quieter and I could get it up to 120 knots. When we got back to Wickenburg, I’d put 1.4 hours on the Hobbs. My client paid for that, as well as for some waiting time.
Two days later, I was in Aguila, doing a job for the maker of a “breadcrumb” communications system. Breadcrumb systems, as they were explained to me, create a wireless network that can be used for voice, data, or video communications. The folks who hired me had an impressive system they wanted to mount in the helicopter. The idea was to have me fly around with the system and a few techs on board to see how well the system stayed connected to other breadcrumbs on the ground and how well video that one of my passengers shot could be seen at ground-based stations.
As the photo here shows, I had to remove both doors on the pilot side so they could mount the unit’s antenna. The breadcrumb box itself was positioned at the feet of the passenger behind me; you can barely see it in this photo because it’s just a flat box standing on one end. Although the unit can be powered by batteries, my helicopter has a 28 volt DC port that looks like a cigarette lighter port. The breadcrumb had a cable that could take this voltage, filter it, and step it down to the 12 volts it needed. So they just plugged it into my DC port. The boss of the operation wasn’t happy about the positioning of the antenna — he wanted to dangle it somehow under the helicopter’s body — but we soon proved that it was fine.
One of the techs also had a GPS and, at first, they wanted to mount it on my tailcone. They claimed that in the work they’d done with RC helicopters, they’d found that there was too much interference from the main rotor disk for the GPS to get a good signal. When I told them that my handheld GPS worked in the cockpit cabin, they decided (to my relief) to give it a try. (For the record, I would not have let them mount it on my tailcone. That’s much too close to the tail rotor! We might have mounted it on a skid if we had to.)
My passengers climbed aboard and we took off, flying circles around their base of operations at Robson’s Mining World. One guy in the back did the video while the guy beside him kept reporting on the status of the breadcrumb: green, blinking green, green, green, etc. We kept in touch with other breadcrumbs on the system at all altitudes and even when we flew behind a mountain. We only lost touch once, and that was for only a few seconds. The video went down to the guys on the ground, who clustered around a laptop set up on the hood of a car in the parking area. We did this for about 20 minutes, then landed.
I didn’t realize it then, but I was done with my assignment. What followed was about an hour spent giving everyone there a ride. I took them three at a time and did a 4-minute ride around the base, climbing up the mountain behind Robson’s and descending back into the desert for landing in my designated landing zone. When everyone had their ride, they told me to shut down and have lunch with them. Some other folks would be taking photos of the setup while I was eating.
I ate outside, with the guys from Rotomotion. They build RC helicopter systems to be used for surveillance and unmanned observation. The company founder started the company when he got frustrated that he couldn’t fly an RC helicopter. (Having owned one for a while, I know exactly how he feels; I couldn’t fly mine, either.) He wrote a computer program that would fly the helicopter for him. His company now builds helicopters that work with his Linux-based software system. They had three helicopters with them: a small electric model (on the table in this photo), a medium diesel model, and a large model powered by a chain saw engine.
The software is extremely cool. Once the helicopter is airborne, the software takes over and can hold it in an absolutely perfect out of ground effect hover. You can also tell it to go to certain coordinates at a certain altitude and it’ll go. It uses wireless communications to control an onboard camera or other equipment. If it loses its radio control signal, it’s programmed to return to its home base. Although they have a routine for software-controlled take off, they need a reliable but small altimeter to judge distance from the ground before a good landing program can be written. I have no doubt that they’ll add this feature soon. These guys definitely know what they’re doing.
While the rest of the group went off to go shooting out in the desert, a small group of us remained to watch the RC helicopters fly. A police officer from Chandler had come up to get a demonstration and we just watched. He said that the system has many applications in law enforcement and he seemed excited about it.
I went home a while later and put my dusty helicopter away. I’d logged 1.6 hours for the assignment — not much, but enough to make it worthwhile. And the technology I’d seen while I was out there was well worth the time spent.