Piracy and Other Things that are not Theft

One of the quickest ways to get a (media) pirate angry is to equate piracy with stealing. "Piracy is not theft!" they cry. Theft removes the original, thus making it so the true owner can no longer use it. But when you pirate something, you're only making a copy. The original is untouched.

Legally and semantically, they're right. Piracy is not theft. But there's a justification implied: that because the owner still has the original, the copier didn't do anything wrong.

We talked a lot in the comments yesterday about how the negative effects of piracy are not as bad as we think, but that doesn't necessarily make it right. For example, here's a list of other things that, like piracy, are also not theft:

1. Hacking into someone's secured wireless network.
2. Breaking into a government facility and copying down top secret information.
3. Sneaking into a movie theater.
4. Forging a plane ticket (unless the plane is full, of course, then you're stealing a seat).
5. Plagiarism.
6. Writing a program that steals rounded-off fractions of financial calculations (yes, like Office Space).
7. Hacking into an Air Traffic Control computer and changing the schedules.
8. Slander.
9. Most acts of federal treason.
10. Kicking someone in the nuts.

So, yes, I agree that piracy is not theft. But that doesn't justify it.

Opinions on Piracy (and Some Data)

I've decided this week is going to be piracy week here at Author's Echo. Not the cool kind of piracy where you swing from the rigging and swash and buckle and stick it to the mean, oppressive, royal navy. But the lame kind, in which copyrights are infringed and authors get all upset over lost sales.

Apparently, I have a lot to say on the topic, but I hope to contain it to three posts (so I don't have to bore you with it again for a while). First, some of my opinions on the subject, so you know where I'm coming from, and maybe where I'm going.

Tomorrow's a little more fun.

• Pirates are not bad people. That has to be said up front. I have lots of friends who pirate stuff (I live in Thailand, remember?), and I still like them. I still like you. And heck, even I sometimes take advantage of "gray areas." Just, uh, don't expect a high five from me because you "stuck it to the man."
• Most arguments for piracy are empty justifications. Just like telling myself I can eat a chocolate cake because I ran a mile today, justifications don't make a bad thing okay. (Note: I don't actually tell myself this. I just eat the friggin' cake and don't run at all.)
• Piracy is illegal. There are gray areas, and some things are legal in some countries, but for the most part, if you download something people usually pay for? Yes, that's illegal.
• Piracy is not worth getting angry about. For one thing, there's no strong evidence that pirated downloads = lost sales. Certainly some are, but I think for the most part, if we magically figured out how to prevent piracy forever, it would result in approximately the same number of sales. Getting angry about piracy, on the other hand, is likely to lose paying customers more than it stops the illegal ones.
• Pirates are not doing authors any favors. It's often argued that piracy leads to new readers. The data (what little there is) doesn't support this argument either. Certainly some pirates turn into paying fans, but most don't, and not enough to justify the practice.

For those last two, Tobias Buckell does a great job discussing the data here. He also sums up his opinion (and mine) thusly:

"I believe piracy [has] a neutral effect from all the studying I've done, but also that standing up to declare you didn't pay for it for whatever mental judo justification you have means you're being kind of a dick." -- Tobias Buckell

To that end:

• As a method of "sticking it to the man," piracy is pretty freaking ineffective. Internet piracy didn't kill the music industry, digital singles did (and they didn't so much kill it as shift where the money is made). And I was pirating virus-ridden, multi-floppy versions of computer games over 20 years ago -- even before the internet -- yet now, the gaming industry is beating the growth of the US economy by about 8x.

To reiterate: pirates are not bad people and I still like you. I don't want to beat up on pirates this week, though neither do I want to imply that piracy doesn't hurt anybody. Mostly I want to be clear that the justifications for piracy are just that: justifications -- something humans are very good at composing.

Feel free to disagree with me in the comments, especially if you've got good (non-anecdotal) data to contradict anything in the links here. Of course, you can agree with me too. We love that sort of thing around here.

Tropes vs. Cliches

A trope (in a story sense) is any plot, character, setting, device, or pattern that we recognize as such. It's kind of everything, from the unassuming farm boy to the rebellion against an oppressive government to the wise mentor to the chase scene in which the car smashes through a pane of glass being carried across the street.

Tropes are what make stories run. A story is not good or bad based on whether or not it has tropes. ALL STORIES HAVE TROPES. A story is good or bad based on how those tropes are used.

What we like about tropes is familiarity ("Yay, ninjas!"), excitement ("Oo, the hero's going to get all awesome on the badguys!"), and especially when our favorite tropes are twisted in interesting ways ("I did NOT see that coming").

What we don't like is when tropes are predictable to the point of boredom. That's when a trope becomes a cliche.

Now, cliches are subjective. What's old and tired to you may be brand new to someone else, or it might be someone's favorite trope--they don't care HOW much it's been done; they love it every time. So how do you keep your stories from slipping past trope into cliche? Here are a few ideas:

1. Be trope-savvy. One of the things I loved about Avatar: The Last Airbender was how it was always aware of its own tropes. Sokka knew he was the comic guy, the plan guy, the boomerang guy, or "the guy in the group that was normal." They knew they were being silly (and yet a little bit serious) when they came up with a name for their group or for the bounty hunter Zuko sent after them.* It worked because they showed you they were aware of their tropes, through action and dialog.
2. Subvert the tropes. I thought Megamind was fantastic because even though it used all the superhero tropes, it never played them straight. It took one of the oldest tropes (villain captures girl, threatens hero, hero outsmarts villain), showed they were trope savvy (girl mocks villain's threats as cliche), then twisted it (villain kills hero?!). And that was where the movie started. That sort of thing kept me guessing the whole time, even though I knew the ultimate end.
3. Don't bother. Seriously, the subjectiveness of cliches is one of the reasons you can't please everybody. One completely viable method of dealing with this is to not even try. Use the tropes you love, put them together in ways you think are awesome, then find the people who agree with you.

What do you think? How can we use the same old tropes (there are no new ones) while avoiding cliche? When have you seen it done well?


* And the fact they never tell you his real name proves even more they know the tropes they're playing with:

Sokka: Wait, YOU sent Combustion Man after us?
Zuko: Well, that's not his name, but--
Sokka: Oh, sorry. Didn't mean to insult your friend!

Dr. Bananas

K. Marie Criddle is challenging herself to draw something every day for a year. It has inspired me--no, not to draw every day, are you INSANE? It inspired me to draw for the first time in 6 weeks (gosh, every time I put a sketch up here, it's been months since my last one...maybe I SHOULD draw something every day *slap* *slap* NO! What, are you INSANE???).

(Yeah, okay, maybe a little).

Her first sketch also inspired me to draw something with a gun for an arm, so I'm not being very original here. But then this is what was in my head. You HAVE TO draw what's in your head, right?

How to Get Me to Unfollow your Twitter Feed

I know this is going to cause a swath of readers freaking out wondering, "Am I good enough? Will Adam unfollow me too?!" Because, of course, you're ALL worried about what I think of you. (That's how it is in my head, at least. Maybe I should see someone about that...).

Okay, so nobody's worried about my follow. But to avoid hurt feelings, I want to lay this disclaimer: I unfollow people rarely, and only when they define themselves by tweets like the ones below. If you do some of these sometimes, but other times post something witty or interesting, or converse with me like a human being (as opposed to a marketeer), then chances are very good you're safe.

But if these are the ONLY things you Tweet, then you might rethink your social media strategy:

• Follow Friday (#FF) lists of random Twitter handles, with no explanation as to why I should follow all these people you crammed into 140 characters.
• Publicly thanking a list of random Twitter handles for the #FF mention.
• Tweeting "Good morning" every time you get on and nothing else.*
• Links to your blog, your book, you, you, YOU.
• Tweet 20 times within a couple of minutes, thus filling my entire timeline with you.

Again, if you sometimes tweet things like this, don't worry. I link to my blog post too (a lot of my traffic comes from Twitter), but I try to keep that from being the only thing I say. The people I drop are the ones who followed me just for the follow-back, who just want to up their numbers even though nobody's actually listening to them, who don't intend to interact or read anyone's tweets but their own.

What behavior on Twitter (or any social media) bugs you the most? What do you LIKE people to do?



* I realize some people use Twitter only for conversation, and "Good morning" is a way to let their followers know they're on and ready to talk, but if I don't converse with you, it's all I see. Besides, we can talk without me following you.

How This Blog Works

At the risk of spoiling the magic, I thought some of you might benefit from knowing how I do things around here. Here goes.

THE SCHEDULE
A long time ago, I wrote posts whenever I thought of them, trying for a vague "once or twice a week." Now I post every Monday, Wednesday, Friday. I don't know if you guys care (because of Google Reader, and living 11-15 hours ahead of the US, I never know when people post), but it makes it easier for me to plan and to know I'm being consistent.

THE IDEA LIST
There is no way I could come up with a blog post idea on the spot three days a week. Shortly after I began a schedule, I started a list of blog post ideas. This takes off tons of pressure, and also allows me to cherry-pick the best ideas. They come in waves: one week I'll have a dozen ideas, the next couple of weeks I'll have none.

THE WEEK BEFORE
I've taken to writing my posts a week ahead of time (right now, it's May 23rd). I usually have all three posts written by Wednesday or Thursday the week before, scheduled to go up between 7-8 PM, my time, on their respective days. Occasionally real world news will inspire a real time post, but not as often as you'd think. As with the idea list, this takes a lot of pressure off me.

THE CHOOSING OF THE POSTS
When I choose a post topic, my general rule (that I made up just for this post) is each post must attempt to be one or more of the following: helpful, funny, interesting (in that order of preference). I try to avoid "housekeeping" posts, which is why you usually don't see blog awards and why I've never mentioned the change in my background picture (um, until now). I also try to avoid rants, albeit with limited success.

THE ACTUAL WRITING
Every post is unique to its own topic, but there are a few things that seem to occur often:

1. I make lists and/or embolden key sentences. That's cuz I know how lazy a reader I am, and I figure other people are the same. It's also because I like lists.
2. I link to myself a lot. I link to other places too, but basically I'm self-centered. Partially because I hate to think those posts are forgotten. Partially because linking to an old post feels better than repeating myself. I know you can't follow all of them, but I hope you click on one every once in a while.
3. I add images. I used to do it only where I needed one, but a lot of feed aggregators (like Blogger's blogroll widget, or the blog apps on Facebook) grab a thumbnail from the post. So lately, if I can think of/find a good image, I'll throw it in to help the post stand out.
4. I try to ask you guys a question at the end. Because unpublished-author blogging is more about getting to know people than anything else. And because when you comment, it makes me all happy inside.

THE COMMENTS
Though I read them all, I'm a little sporadic with replying to comments. It depends how many comments I have to respond to and how late the girls are to school and how many boys hit how many other boys that morning. Besides, I'm pretty sure my lame replies aren't why you come here. I've been experimenting with replying to comments via e-mail (for those of you who allow that in your Blogger profile), and I have to admit, it's a lot easier and feels more personal. If I learn anything else useful, I'll let you know.
 
THE TIMES REAL LIFE GETS IN THE WAY
I try to save funny pictures, question/answer times, and short posts for those weeks I need something quick, or when I just want a bit of a break. Once or twice a month I'll remix a post for my sanity (I like "remix" better than "repost," especially since I usually update them before reposting), but never one younger than a couple of years. If I need a longer vacation, I'll go with guest posts or in extreme cases, a 1-2 week hiatus.

There. Now you know what goes on behind the bamboo curtain. Hopefully you can forget you know all that now, so you can still pretend I'm cool.

How do you blog?

When (and When Not) to Prologue

(Remix)

There are three things that make something a prologue:

1. It comes before the first chapter.
2. It is a part of the story (as opposed to an introduction, preface, or forward, which are about the story, but not part of it).
3. It says "Prologue" at the top.

Simple, right? That's what makes something a prologue instead of, say, "Chapter One," but it doesn't explain what makes a good prologue. That's what this post is about.

WHEN NOT TO PROLOGUE
A lot of writers use prologues as a band-aid for a bad beginning. This doesn't work (I'll explain why in a second). It actually has the opposite effect, to the point where some people skip prologues entirely. TIP #1: Don't use a prologue because you need a better beginning. Fix your beginning.

There are generally two kinds of band-aid prologues. The first is the FALSE ACTION SCENE, in which the writer is told he should start with action, so he inserts a scene that has nothing to do with the inciting incident. Sometimes the writer will use a flash-forward, inserting a tense scene from the climax and letting that be the tension that drives the reader through their boring beginning.

The reason this doesn't work is because starting a story is hard, and when you add a prologue, you require the reader to start your story twice. TIP #2: Don't use a prologue just to suck the reader in. You'll only have to suck them in a second time when the prologue's over.

The second band-aid prologue is the BACKSTORY INFODUMP. This happens when the writer is afraid the reader will become lost without all the background. Sci-fi and fantasy are notorious for this. A good genre writer, though, is able to mix telling details into the story so they don't have to put it all up front in one big exposition. TIP #3: Don't use a prologue to explain the world or backstory or any other kind of telling exposition. 

 Once again, George Lucas shows us what not to do.

WHEN TO PROLOGUE
Despite their downsides, I like prologues. Used wisely, they can be very effective. Here are some situations in which a prologue can be useful.

1. To show a point of view that doesn't appear anywhere else, or doesn't appear until the end. For example, if you need to dramatize some event the protagonist never witnesses, like, say, the mysterious circumstances of their birth.
2. To create tension that the protagonist is not immediately aware of. This can be especially effective in mysteries and thrillers, where the real tension (e.g. When will the killer strike next? Will the protagonist learn the truth before the killer comes for him?) is behind the scenes. Then the opening scene, in which the protagonist is going through their daily life, is flavored by the tension that the reader knows something is wrong.
3. To manage the reader's expectations about your story. Have you ever read a story that was all dragons and swords and magic, only to discover the evil villain is a space alien with his own spaceship? Genre blending like this can be done well, but if it's done poorly you end up sucker-punching the reader. A prologue establishing that your fantasy world is a forgotten Earth colony, or that "God" in your story is an intelligent super-computer orbiting the planet, can sometimes go a long way towards easing the reader into the weirdness.

Keep in mind, though, that these are all guidelines. There are no rules in this business. That's why the best tip is this one, from the illustrious Nathan Bransford:

Take out the prologue and see if your book still makes sense. If it does, you didn't need it.

What do you think about prologues? Love 'em? Hate 'em? To the comments!