Social Networking Stupidity, Part I

Is your social networking activity making you look like a jerk?

I just had to blog this. It’s such a great example of someone really screwing up with social networking.

A local area magazine (I’d rather not mention its name since I don’t want readers to trace the idiot who is the subject of this post) did its annual article on the 50 best places to eat in the state. Just today, it posted on its Facebook page:

Since our April issue was published, we’ve received numerous emails from readers who have informed us that two of the restaurants we included in our “Best Restaurants” feature have closed: [redacted 1] and [redacted 2]. Both restaurants were open at press time, and we regret that our very long lead time might lead to some disappointed readers.

One of the page’s followers commented:

Sounds like you need a new contributing writer~I’m available!:)

After a few other comments from readers, the editor replied:

Doesn’t have anything to do with the writer, [redacted]. She’s one of the best in the business. It’s because of our long lead times.

I can understand that. The magazine is, after all, a print publication. It’s not as if you can create the content and distribute it a week later.

But the commenter didn’t stop there. She fired off two more comments in quick succession:

I would beg to differ! A good writer would have given the editor the heads up. It’s not just about coverage, it’s about follow up too. I know she can write, but is she paying attention?????

and

btw–EVERYONE who lives in [redacted 2 town] knows how long [redacted 2] has been closed, not buying the excuses.

Whoa. I couldn’t let that one go. I have a lot of respect for the publication and the difficulty of remaining up-to-date in print. So I replied:

Give it a rest, [redacted]. [redacted magazine] does have VERY long lead times. Stuff happens. Also, its not likely you’ll get hired on as a writer with an attitude like that. Cut them some slack!

Within an hour 8 people had “liked” my comment, so I know I wasn’t far off-base. Another commenter suggested she try Xanax.

The point of all this is, this woman posted a slightly critical comment that was basically asking for a job. When the editor defended his publication against the criticism, she fired away with more critical remarks. (And don’t even get me started on the idea of a “writer” using five question marks at the end of a sentence.) Is this the way she does her job hunting? Her comments make her look like a real jerk. Who would hire her?

This was today’s example; I’ll likely follow this up with more examples as I stumble across them on the ‘Net.

Protecting My Work

Site changes to images, file links, and RSS feeds.

Well, I’ve had enough. Enough of people using my images on their sites or trying to pass them off as their own. Enough of people hot linking to content on my site, forcing me to host images and files for them. Enough of feed scrapers stealing entire blog posts and using them to fill their sites with content.

So I’ve made some changes to this blog:

  • Through the use of a WordPress plugin called No Right Click Images Plugin, you can no longer right click on an image to display a context menu and download it to your computer — or do anything else with it. As an added bonus, you can’t drag it off the Web page and onto your desktop to save it either.
  • Through the use of some new code in my .htaccess file, if you embed an image hosted on my server in a Web page or use it in a blog post, e-mail message, or other location, you’ll see a message like the one shown here, telling the viewer that the content must be viewed on this site.
  • Through the use of a WordPress Plugin called Download Protect, you can no longer use a direct link to PDF or other selected files on this site. To download the file, you must go to the page on which its link appears and use that link to download it. This prevents file leeching — folks linking directly to a file hosted on my site, sucking my bandwidth without visitors ever seeing the post related to the file.
  • And finally, after a long run with full RSS feeds, I’ve switched back to summary feeds. This means that instead of being able to read entire blog posts from this site in your feed reader, you can now only read the title and summary. You’ll have to click a link to read the post and see its images. Although I’ve been using one-line summaries for all blog posts for a very long time, I’ll do my best to expand those summaries so readers know what they’re missing by not visiting the site.

I do want to remind everyone that the contents of this blog are copyrighted. I have every right to protect my work.

Internet content theft is possibly the biggest problem that original content creators like me face every time we add content to our sites. While these measures won’t prevent all content theft, they will make it a bit harder for thieves to steal my work.

Hopefully, these measures will also encourage more site visitors to interact with me and other visitors, share feedback, and encourage me to produce more interesting content.

Your feedback is welcome; use the Comments link or form for this post.

February Needs More Days

We are experiencing scheduling difficulties. Please stand by.

Ever have one of those months where there just aren’t enough days? We all say that about February — mostly because it usually only has 28 of them — but even if it had its full share, it wouldn’t be enough. Mine is booked solid.

Want a glimpse of what my work/personal life is like right about now? Here’s the bullet point edition:

  • I have two chapters left to write on a book I’ve been struggling to finish since November. Part of the problem was that my editor didn’t seem to take much interest in the project, which led me to feel much the same way. Now, of course, they want it done already (as they should) and I also feel the same way.
  • One of my other publishers suggested a topic for a brand new book for them. I need to come up with an outline and make contact with the public relations person for the software company to see what kind of support I might be able to get from them.
  • That same publisher is gearing me up for a revision of my Mac OS X book for Lion. That book, which I also do layout for, has a brand new look, requiring a new template and mindset.
  • Another publisher is making noises about another revision for another project. I’m think it might be pretty far out on the horizon, but I need to chat with them about needs and scheduling.
  • AircraftOwner Online has announced that my monthly article deadline is now the 12th of the month rather than month-end.
  • I’m under contract to write two more articles (that I keep putting aside) for a Web publication. I won’t get paid for the first one I wrote (last year) until I hand in these two.
  • One of my aerial survey clients wants a 1-2 day wildlife survey flight in northern Arizona next week. (This just popped up today.)
  • One of my aerial photo clients has booked a 4-day photo flight in Arizona and Utah for mid-month. The flight requires me to obtain permits for flying low level in three different national parks. (And yes, one of them is the Grand Canyon. Wish me luck.)
  • I have to drop off my helicopter for its 100-hour inspection in Mesa, AZ; a few days later, I have to pick it back up. I also have to hope there’s nothing wrong with it that would prevent me from picking it up on time.
  • I have an FAA Part 135 check flight scheduled near month-end.
  • I have a day trip to Sedona scheduled near month-end.
  • I have a week-long vacation in the Bahamas with my husband. (A business trip for him; a chance to breathe for me.)
  • I have to drop off and then pick up Alex the Bird from his boarding facility before and after the vacation.

Get the idea?

You might have noticed that blogging does not appear anywhere on this list. That’s not a mistake. Blogging falls very low on the priority list. So low, it doesn’t even appear on lists. So this might be the only original blog post you see for quite a while.

Just thought it fair to warn you. This is going to be a very long short month.

And who says freelancers don’t work hard for a living?

Dragon Dictation? Maybe.

I try an iPad-based dictation tool.

Note: This blog post was dictated into my iPad. Although I’d originally hoped to display the text in two columns to show unedited and edited text (as referred to in the post), I later decided to use DEL and INS tags to show actual text edits required — places where Dragon Dictation actually got it wrong. I did not correct my failure to dictate punctuation or my poor use of words, since those are my errors and not the software’s. A few additional comments are included in square brackets in the text.

I am trying something different today. I’m writing a blog post by dictating into my iPad.

I’m using a program called Capps dDragon caps dDictation. I downloaded it for free on my iPad not long after I bought the iPad. I’ve tried it a few times, and was very pleased with the results. Unfortunately, there’s a lot more to using dictation software and than simply saying what you want to say.

These first two paragraph are good example. On the left you see my dictated version. On the right you see my edited version. Notice the changes I needed to make. It’s really not bad, but not exactly perfect.

The main problem with using dictation software. See is that you have to dictate everything you want to type. That means you have to dictate your punctuation, capitalization, quotes, and any other information that you want to put in your text other than the exact words.

You also need to speak clearly directly into a microphone. On the iPad that’s not exactly convenient since the microphone is at the top of the iPad. Right now my iPad is standing up on my table with the microphone close to my mouth so that so that Dragon dictation can understand what I’m saying. Of course if you have an external microphone it will work with that as well.

You also need to be careful about what you say. Any mistakes you make will be transcribed. This makes dictation a useful tool for getting out of a first draft, but not for getting final text. You’ll still have to go through the document and make changes to it as necessary to correct errors and rephrase sentences.

As I dictate this today, I see that I’m quickly getting the hang of it. Although it’s not natural for me to do this, I don’t think it will be difficult to learn. What amazes me the most, is the way the software can recognize exactly what I’m saying. I haven’t edited any of this text other than what you sought saw at the top of this post. [Not true; read note at top of post.] Get Yet as you can see dragon dictation has managed to understand almost everything that I’ve said. This absolutely amazes me. What I don’t understand, however, is how many people reported that dragon dictation could not understand them. The overall reviews in the iTunes store for the app are very low. I can only assume that these people are not speaking slowly and clearly so that the software can understand them.

What I do find a little bothersome about this software is that it needs an Internet connection to work. As I speak it evidently records what I say and then when I’m done it sends it to the Dragon dictation website words where it’s translated and returned to me. This isn’tthe best solution if you don’t have an Internet connection all the time. But given the price of the software, which was free, I really can’t complain.

Another thing I find a little bit bothersome is the fact that it evidently has a buffer. I can’t just go on talking for a long period of time and expect the software to be able to translate. Instead it automatically cuts me off gets the translation in and puts it in the software sometimes while I’m still talking. [Boy, that previous sentence could sure benefit from some commas.] This means that I need to stop at the end of every long paragraph let it translate and then start again.

It’s interesting to me also how the software does not recognize upon a pause as a place to put a comma or period it’s also interesting to me that it probably just inserted those two forms of punctuation instead of the words that I just set. Let’s see. That’s funny it’s got the words as I said them and didn’t put in punctuation. I guess it does take a little bit of time to get used to this. [This whole paragraph is a good example of experimenting. Believe it or not, Dragon dictation made only one error; the other errors were mine.]

As a writer, it’s a dream to be able to say what you want to say and have it automatically typed for you. But the reality is and not so sweet. In reality, I can type a lot faster than I can do this dictation. I can also make a lot fewer mistakes. And I can edit as I go along.

Still, I think the thing that bothers me the most, is that I have to stop at the end of every long paragraph to let Dragon dictation catch up. I don’t type like this. I don’t think like this. I tend to type thing [I corrected myself here but DD didn’t know that.] right write a lot more a lot more fluidly. I also don’t think about the comments commas that I need to put in my documents.

Overall what do I think of this? I think it has its uses, but I can’t see using it as a normal writing tool. I’ll keep experimenting with it, but I’m not sure whether it will ever be something I use daily.

If you have an iPad or my phone iPhone I recommend giving this a try. You might like it. And if you like it a lot. You might want to buy the regular software that they self sell for your computer. They have a Windows version and a Mac version.

On Bad Fiction

Practice before you publish.

I read some very bad fiction today. It reminded me why so many writers can’t seem to get published.

They suck.

The story was a short mystery in a magazine I downloaded into my iPad from MagCloud. I blogged about the free content there just the other day. Now I feel as if I should add a disclaimer to that post: Some content may not be worth the time it takes to download.

The thing you need to know about MagCloud is that it’s a tool sometimes used by self-publishers to get their content published. In this case, someone had put together an anthology of short fiction in a “Special Short Story Edition” of their magazine. The magazine itself is poorly designed, featuring dense lines of tiny print and low resolution images — yes, I do mean pixelated images; you know resolution has to be very low if a photo doesn’t look good on an iPad. The images have nothing to do with the stories. Not at all. Well, I should amend that description. Not all of the stories were dense lines of small type. Some were rather spacious. There was really no consistency in the magazine’s layout. It was the most amateurish thing I’ve seen since the days of typewriters and wax pasteups.

I don’t know where the editor got the stories he put in the magazine. Maybe he created a contest. Maybe these people actually paid an entry fee to “win” a place in the 60-page PDF that would cost a whopping $13.95 plus shipping to get in print. But that’s beside the point.

The point is that I read one short story and it was bad. Very bad.

There are three points that made the story bad and they repeated themselves throughout the story: author voice, missing information, and factual inaccuracies. Let’s take a look at each.

Author Voice

I am a huge believer that the author’s voice should not distract the reader from the story. The author is narrating — telling the reader what’s going on. She’s setting a scene, describing action, reporting dialog. As you read the author’s words, you should be able to step into the page (so to speak) and see and hear what’s going on.

Good writers can do this. Great writers can do this even when editorializing along the way.

But bad writers absolutely suck at doing this. They’re so hung up on writing the descriptions, using the right words, reporting the things they think will bring the scene alive. They so obviously write with a thesaurus nearby.

Take this opening passage:

Detective Emma Knightwood sighed heavily as she stared at the body lying only inches in front of her sensible brown shoes. Emma was a petite woman of fifty-four, with salt and pepper black hair and green eyes. Although it was nearly midnight, her ivory silk blouse with the elaborate lace bow looked as fresh as when she’d put it on that morning and she never would have admitted that she was perspiring beneath her brown tweed suit. Emma was as frugal and exacting as a miser slowly counting his piles of gold and her support hose had been carefully darned several times over, rather than being replaced with a new pair.

This is the opening paragraph of the story. The paragraph that’s supposed to be “the hook.” I’m not hooked. I’m turned off by a cheap spinster detective wearing brown and darned support hose.

But here are some specific problems:

  • The first sentence mentions that Emma was looking at the body that lay at her feet, but the remaining lines of the paragraph don’t mention the body again at all.
  • Is her hair salt and pepper or black?
  • How is it that her silk blouse can look fresh at midnight if she put it on that morning and she’s sweating?
  • Why wouldn’t she admit she’s sweating? Is that a character trait?
  • What’s with the miser counting gold? That run-on sentence takes the reader away from the character and the story before bringing the reader back to the character.
  • This is the opening paragraph of the story. Do we really need to know all these details about this main character now? Or ever? Nothing else that comes later in the story refers to any of this.

Here’s a bit more, with dialog. It comes after a few paragraphs about the victim, the fact that there have been multiple murders lately, and an introduction to Emma’s partner, Detective Stanton Reynolds. Reynolds has just asked Emma what she thinks.

Emma straightened and pushed her wire rimmed glasses up her small nose. “I don’t know. Read me the summary of the victims again.”

“Okay,” Stanton replied, flipping through the pages in his small blue book. “The first victim was Ophelia Danworthy, age sixty-eight, married with four children, retired. The second and third victims, Candace Winters and Henry Simpson, worked together in the same jewelry story and were killed while attempting to make the store’s nightly deposit at a bank. Ms. Winters was single, unmarried and Mr. Simpson was a bachelor, nearing retirement.”

“No signs or a robbery attempt on the store employees?” Emma queried.

“None. The bag of money and deposits was found with the bodies. Victim number four was Sophie French, age thrity-four, a successful businesswoman, unmarried and no children.”

“And now Rachel Zerinsky,” Detective Knightwood sadly mused aloud.

This, like most of the rest of the story, is screaming at me in the author’s amateurish voice, preventing me from getting into the story, forcing me to nitpick every sentence.

  • Emma’s nose is small here, but it’s also slender a few paragraphs later when she does the glasses poke again.
  • Ophelia Danworthy? Rachel Zerinsky? Oddball names for no reason can be distracting, too.
  • Ophelia was 68 and she had four “children”? I hope they were grown children.
  • Emma’s “query” about signs of robbery is so obviously contrived as a way to pass information to the reader using dialog. Emma would have to be a pretty crappy detective to forget that the jewelry store employees were not robbed when a “bag of money” was found with them.
  • “Queried” and “sadly mused aloud” are two examples of overstated dialog attribution. If you’re not sure what I’m talking about, Google “dialog attribution” and see what comes up. Although I don’t completely subscribe to the “he said,” “she said” school of dialog attribution, I agree that using an excess of odd attributions — especially combined with adverbs — is extremely distracting. (Stephen King’s On Writing goes into this in a good amount of detail.)

The author attempts a lot of character development through dialog and by telling the reader about the characters. In doing so, she inserts so much of her voice that the reader can’t get into the story. She needs to learn more about what some people call the first rule of writing: Show, don’t tell. According to Wikipedia,

Show, don’t tell is an admonition to fiction writers to write in a manner that allows the reader to experience the story through a character’s action, words, thoughts, senses, and feelings rather than through the narrator’s exposition, summarization, and description. The advice is not to be heavy-handed, but to allow issues to emerge from the text instead, applies to non-fiction writing too.

Heavy-handed is the phrase I’d use for this author’s work.

Missing Information

One of the rules of mystery writing is called “fair play.” Fair play means that the reader gets all the clues the detective has. This is so the reader can solve the mystery or at least understand how the detective solved the mystery.

This author fails at fair play.

  • In the beginning of the story, she mentions “strange clues” left behind at the scene of each crime but never details what these clues are.
  • Later, when a diamond is found at the murder scene, she talks with her partner about the “stones found at the scene of the crime.” Are those the strange clues?
  • The analysis of the clues are far beyond the capabilities of an average person.
  • The murderer is identified during a dialog that presents new information unavailable to the reader. A name is thrown out as they race to the next victim’s apartment and, sure enough, he’s the killer.

To make matters worse, there are no real red herrings — clues that lead to false conclusions. There’s no challenge to the story, nothing to make it interesting.

Factual Inaccuracies

This story has more than its share of factual inaccuracies.

  • The murder victim described at the beginning of the story was supposedly bruised from being beaten with a strand of pearls after death. Although the story does not mention how long the victim had been dead, bruises for injuries inflicted before death can appear as red or blue flesh for the first five or so days after death. Bruises for injuries inflicted after death do not appear in color. This is likely due to the lack of blood flow after death. This document explains. (It took 10 minutes for me to confirm this using Google.)
  • Another police officer calls out to the detectives: “Mr Reynolds? Miss Knightwood?” If they are detectives — as they were both introduced to the reader earlier in the story — they would be addressed by fellow police officers as “Detective Reynolds” and “Detective Knightwood.” Even television can teach you that.
  • A diamond in the story is referred to as huge. Emma says, “It must be at least three carats, maybe more.” Sorry, Emma. Three carats is not “huge.” I wear a full carat on my finger and it’s smaller than the size of a pea. Two carats would be a fat pea. Three would still be smaller than a chick pea (aka garbanzo bean). Now if you were talking ten carats — well that would start getting closer to huge — for a diamond, anyway.
  • When a set of clues resolves into a series of numbers — 878910 — the detectives automatically assume they’re “latitude or longitude in hours, degrees and minutes.” Whoa. First of all, no latitude or longitude in the U.S. starts with 8 or 87. While it’s true that the coordinates could refer to a place in another country, that’s a pretty far leap for the detectives — especially ones who refer to coordinates in terms of hours. Latitude and longitude is measured in degrees, minutes, and seconds. There are no hours.
  • Here’s where the author’s spelling checker failed her: “Devon held Miss Barron in front of him like a shield, pressing the point of a long butcher knife over her juggler vein as his brown eyes shifted from one officer to the other.” [Emphasis added.] I think she means jugular vein. Oops. At least I got a good laugh.
  • Back to the diamond. Emma taunts the murderer by insulting the way he cut the diamond. (He’s supposedly an expert diamond cutter.) She says, in part: “Some of the facets are incorrect and you’ll have to admit, your cut is a little shallow, as well.” Huh? Putting that aside, she goes on to say, “You can always break it and try again.” Break a diamond to recut it? What the hell is she talking about? She then tosses the diamond into the air and the murderer lunges for it — apparently to prevent it from breaking. The diamond bounces on the “hardwood floor” and is unharmed. What else would we expect? A diamond is one of the hardest substances known to man. It isn’t going to break by being dropped on a hardwood floor. An expert diamond cutter would certainly know that, so why is it that he “lunged sideways to catch the diamond before it hit the floor”? Could it be that the author hasn’t got a clue about diamonds?

Bad is Bad

I could continue tearing this story apart, but I think I’ve done enough to make my point. This author:

  • Does not have good writing skills.
  • Is not true to her genre.
  • Does not know how to do research (or is too lazy to do it).

The resulting story is amateurish, almost to the point of being funny. In all honestly, the only pleasure I got from it was tearing it apart as a lesson to myself and anyone who might be interested in writing quality fiction. It’s a perfect example of how not to write a story.

I know I’ve quoted a lot of text from the story, but I’ve done so under the guidelines of fair use, presenting the material in an editorial manner. I have not mentioned the name of the author or the publication so as not to embarrass either one. If the author or publisher read this and want to be mentioned by name, please let me know and I’ll do so. Just don’t expect me to modify this post beyond that. There are lessons to be learned here.

Now excuse me while I purge this crap from my iPad.