The Failure of Secrecy: The alpha, leaks, and the WoW community
The past few days have seen leaks on an unprecedented scale. For better or worse, nearly the entire visual artwork of the expansion is out on the internet, and key and yet-unseen components of the lore, landscape and mechanics are now laying wide open for those who care to look. Many people have drawn lines in the community -- some believe these leaks are good, and others believe them bad.
In both camps, basic information is lacking as to exactly what leaks are, how and why they originate and what they mean for the common player. It's critical that we as a community take an introspective look at what these leaks mean to us, why they happen and the consequences we all face as a result.
Let's begin this examination with a basic question ...
What are leaks?
At the most basic level, leaks are previously unreleased information given to the press with the intention of distribution to the public. In the case of WoW, a leak can range from a release date for a patch to an entire client of a new expansion. Leaks like these comprise of data that are accessible publicly, one way or another, and are generally not considered trade secrets.
Another type of leak, which is much more serious, is something like the source code to Windows 2000. Something that like is very sensitive and has a lot of real-world implications. WoW doesn't have anything secretive like that which can impact the very security of our computer networks and commerce infrastructure, even though WoW leaks are important to Blizzard in their own regard.
NDAs, C&Ds, beta and alpha-bet soup
When dealing with leaks (and particularly recent events), there are a few terms that generate a lot of confusion. Let's clear them up.
Non-Disclosure Agreement: The mystical NDA. This is a legally binding contract that says you cannot release the information you're given. If you break the contract, there are real-world consequences. People who work at Blizzard are under an NDA. You are not under an NDA unless you sign one.
Cease and Desist Order: The C&D. This is an order issued by a judge that says you must stop doing something you're doing. You have to follow it, or else you're going to face serious, life-changing consequences. If you violate an NDA and publish information, you'll get a C&D order that requires you to take down the information ... or else. A C&D order is different from a C&D letter; a letter can be issued by anyone, but doesn't carry any judicial mandates.
Alpha: A game that is in early development; probably is under an NDA.
Beta: A game that is in the later stages of development; may or may not be under an NDA.
The Cataclysm alpha
Going on now is a massive and unprecedented leak of information from the Cataclysm alpha by MMO-Champion and the Nihilum Cataclysm Wiki. They are uncovering literally every upturned stone, every deformed building and every crack in the land. This leak will go down in history as one of the largest and most complete game leaks ever.
The Cataclysm client and associated files came from publicly accessible download sources Blizzard made available for those people participating in the alpha. We're not going to link to it or tell you how to get it, but the Cataclysm alpha client is now in the wild. People can download the data to their home computer, fire up a model viewer and go to town.
The story of the Cataclysm leaks is unfolding, and it could take some interesting twists and turns. No one knows where this will all end yet. But we do know how we got here.
It began with leaks leading up to BlizzCon 2009, progressed to a long information "dark age" during which Blizzard barely said anything of substance about Cataclysm, and ultimately resulted in this week's super-massive spoilers. The path from hyper-speculation, to hearing nothing to, hyper-sensitivity is clear, and it's a leading factor in the huge interest generated as of late.
Reactions to the current leaks have been mixed. Some sites are eating up the information; others are swearing off. Blizzard has sent out heavy-handed letters to official fan sites (WoW.com has no official relationship with Blizzard, and we are not a Blizzard fan site) telling them that they can't publish any information still under the NDA, or they'll have their fan site status removed.
Blizzard is deleting forum posts about this left and right. You can't mention some sites on the official forums right now without your post likely being deleted. If you post leaked information, you're banned. They have every right to do this, of course, because these are their forums, but still -- this level of message control is a bit odd when people can access the information so easily elsewhere.
Improving the system
Personally, I don't like leaks. They are a necessary evil in our business, but they encourage too much cloak-and-dagger behavior that in many ways can hurt the community it wishes to support. People behave like children in a candy store over leaked info, and when the candy store has 11.5 million people running around screaming, it gets to be a bit much.
More so, people are banned and suffer consequences not because of ill intent, but because they don't know about NDAs and the system in general. They don't know that they're tasting forbidden fruit and are unaware they might end up on Blizzard's bad side. Good fans of Blizzard's games are punished. This is a key and important consequence of the current system.
Given that fan sites (both official and unofficial), Blizzard and everyone else involved in the creation of this community is here to provide a greater service to the millions of players enjoying the game, Blizzard can take steps to eliminate leaks -- or failing that, deal with them in a better manner. It's key that they address both the root causes of the leaks and the resulting consequences. This requires addressing a number of different situations that, when solved together, will make things much better for everyone involved.
First, Blizzard can be sure to listen to their employees' concerns. A series of leaks back in January was the result of a group of employees being very concerned about pressure being applied to them by their managers. They didn't feel as if they were being listened to and turned to outside organizations to get the word out about the problems they saw. In the past week we've seen leaks from Blizzard employees because they don't feel their company is being forthcoming enough with the community.
Second, Blizzard can stop doing alphas under NDAs. It's been proven that with a game this large clandestine approaches to data management just don't work. Word spreads around Twitter and unofficial forums about leaks nearly instantly -- and when this information is out, it can't be brought back in. There is no "delete" button on the internet.
Third, the amount of open and honest communication from Blizzard needs to sharply increase -- both internally and externally. Let's start with the internal communication. I'm told that a lot of times, people working at Blizzard don't know the whole story. They don't get told everything and are left piecing bits of information together to help form a holistic view of the situation. This leads to situations such as the January 2010 news when we incorrectly stated the public alpha was going to happen. A new alpha was happening, and a new, big client build was being pushed internally that was, by all accounts (and there were many), ready for public/external alpha distribution. Except it didn't go out. The information our group of people was getting from Blizzard themselves was only partially correct. The alpha stayed internal. Better internal communication would lead to less desire to leak things to the community, since everyone would know short and long term publicity plans. If Blizzard employees knew the plan was to announce a major development in two weeks, they'd have a lot less need to leak it early when they're not assuming the information would never be released, or released in months.
Blizzard's external communication can also improve by being more open and honest about release dates and testing phases. We've seen a vast improvement in this area over the years, but they still don't officially acknowledge a release of a patch until the downloader is going and people can already tell for themselves. The lack of official information leads to people's leaking the patch target release date weeks ahead of time, always published on major sites. We knew well in advance when patch 3.3 was going to drop; nearly everyone who visits any WoW site other than the official one knew.
The other result of the lack of external communication is the frenzied excitement that builds around any information Blizzard gives. This is great for their marketing campaigns, but fails when they let the lack of information drag on for so long that people are compelled to leak things. The fruit dangling in-front of those who publish leaks becomes, eventually, too great to resist; serviced by people who don't believe Blizzard is doing a good enough job at keeping the community informed. The lack of information, and the build-up to the release of that information, ultimately backfires on Blizzard.
Fourth, and perhaps most importantly, it's time that Blizzard stop burying their heads in the sand over leaks and unreleased information. It doesn't work to deny the situation. One solution would be to at least say, "Yes, it's out there. But we don't want to talk about it." An even better approach would be to start talking about what's done and not done yet in the leaked info. (A blanket answer of "it's all not done" doesn't work. While everything might be changed slightly, people shouldn't be incorrectly led to hope that the Super Awesome Super Shot XL10 may be buffed substantially when there's actually no chance of it.)
I do want to take a second to note here that in minor ways, Blizzard has acknowledged the leaks exist -- but they still won't address them any farther than to repeat the same tired legal line ("We don't discuss anything under an NDA"). They have reiterated there are only certain things people can talk about (with regards to published Cataclysm content) on their forums, and those things are only items which they've (the blues) have posted either on the forums or on the official site. This level of content distinction, is well, silly.
I write this editorial on leaks and communication not to bash Blizzard or to undermine the game and the community that surrounds it; I'm writing this to clarify the system of politics that goes into something like this. If this subject matter were better understood by the entire community, then we'd all be better off.
In both camps, basic information is lacking as to exactly what leaks are, how and why they originate and what they mean for the common player. It's critical that we as a community take an introspective look at what these leaks mean to us, why they happen and the consequences we all face as a result.
Let's begin this examination with a basic question ...
What are leaks?
At the most basic level, leaks are previously unreleased information given to the press with the intention of distribution to the public. In the case of WoW, a leak can range from a release date for a patch to an entire client of a new expansion. Leaks like these comprise of data that are accessible publicly, one way or another, and are generally not considered trade secrets.
Another type of leak, which is much more serious, is something like the source code to Windows 2000. Something that like is very sensitive and has a lot of real-world implications. WoW doesn't have anything secretive like that which can impact the very security of our computer networks and commerce infrastructure, even though WoW leaks are important to Blizzard in their own regard.
NDAs, C&Ds, beta and alpha-bet soup
When dealing with leaks (and particularly recent events), there are a few terms that generate a lot of confusion. Let's clear them up.
Non-Disclosure Agreement: The mystical NDA. This is a legally binding contract that says you cannot release the information you're given. If you break the contract, there are real-world consequences. People who work at Blizzard are under an NDA. You are not under an NDA unless you sign one.
Cease and Desist Order: The C&D. This is an order issued by a judge that says you must stop doing something you're doing. You have to follow it, or else you're going to face serious, life-changing consequences. If you violate an NDA and publish information, you'll get a C&D order that requires you to take down the information ... or else. A C&D order is different from a C&D letter; a letter can be issued by anyone, but doesn't carry any judicial mandates.
Alpha: A game that is in early development; probably is under an NDA.
Beta: A game that is in the later stages of development; may or may not be under an NDA.
The Cataclysm alpha
Going on now is a massive and unprecedented leak of information from the Cataclysm alpha by MMO-Champion and the Nihilum Cataclysm Wiki. They are uncovering literally every upturned stone, every deformed building and every crack in the land. This leak will go down in history as one of the largest and most complete game leaks ever.
The Cataclysm client and associated files came from publicly accessible download sources Blizzard made available for those people participating in the alpha. We're not going to link to it or tell you how to get it, but the Cataclysm alpha client is now in the wild. People can download the data to their home computer, fire up a model viewer and go to town.
The story of the Cataclysm leaks is unfolding, and it could take some interesting twists and turns. No one knows where this will all end yet. But we do know how we got here.
It began with leaks leading up to BlizzCon 2009, progressed to a long information "dark age" during which Blizzard barely said anything of substance about Cataclysm, and ultimately resulted in this week's super-massive spoilers. The path from hyper-speculation, to hearing nothing to, hyper-sensitivity is clear, and it's a leading factor in the huge interest generated as of late.
Reactions to the current leaks have been mixed. Some sites are eating up the information; others are swearing off. Blizzard has sent out heavy-handed letters to official fan sites (WoW.com has no official relationship with Blizzard, and we are not a Blizzard fan site) telling them that they can't publish any information still under the NDA, or they'll have their fan site status removed.
Blizzard is deleting forum posts about this left and right. You can't mention some sites on the official forums right now without your post likely being deleted. If you post leaked information, you're banned. They have every right to do this, of course, because these are their forums, but still -- this level of message control is a bit odd when people can access the information so easily elsewhere.
Improving the system
Personally, I don't like leaks. They are a necessary evil in our business, but they encourage too much cloak-and-dagger behavior that in many ways can hurt the community it wishes to support. People behave like children in a candy store over leaked info, and when the candy store has 11.5 million people running around screaming, it gets to be a bit much.
More so, people are banned and suffer consequences not because of ill intent, but because they don't know about NDAs and the system in general. They don't know that they're tasting forbidden fruit and are unaware they might end up on Blizzard's bad side. Good fans of Blizzard's games are punished. This is a key and important consequence of the current system.
Given that fan sites (both official and unofficial), Blizzard and everyone else involved in the creation of this community is here to provide a greater service to the millions of players enjoying the game, Blizzard can take steps to eliminate leaks -- or failing that, deal with them in a better manner. It's key that they address both the root causes of the leaks and the resulting consequences. This requires addressing a number of different situations that, when solved together, will make things much better for everyone involved.
First, Blizzard can be sure to listen to their employees' concerns. A series of leaks back in January was the result of a group of employees being very concerned about pressure being applied to them by their managers. They didn't feel as if they were being listened to and turned to outside organizations to get the word out about the problems they saw. In the past week we've seen leaks from Blizzard employees because they don't feel their company is being forthcoming enough with the community.
Second, Blizzard can stop doing alphas under NDAs. It's been proven that with a game this large clandestine approaches to data management just don't work. Word spreads around Twitter and unofficial forums about leaks nearly instantly -- and when this information is out, it can't be brought back in. There is no "delete" button on the internet.
Third, the amount of open and honest communication from Blizzard needs to sharply increase -- both internally and externally. Let's start with the internal communication. I'm told that a lot of times, people working at Blizzard don't know the whole story. They don't get told everything and are left piecing bits of information together to help form a holistic view of the situation. This leads to situations such as the January 2010 news when we incorrectly stated the public alpha was going to happen. A new alpha was happening, and a new, big client build was being pushed internally that was, by all accounts (and there were many), ready for public/external alpha distribution. Except it didn't go out. The information our group of people was getting from Blizzard themselves was only partially correct. The alpha stayed internal. Better internal communication would lead to less desire to leak things to the community, since everyone would know short and long term publicity plans. If Blizzard employees knew the plan was to announce a major development in two weeks, they'd have a lot less need to leak it early when they're not assuming the information would never be released, or released in months.
Blizzard's external communication can also improve by being more open and honest about release dates and testing phases. We've seen a vast improvement in this area over the years, but they still don't officially acknowledge a release of a patch until the downloader is going and people can already tell for themselves. The lack of official information leads to people's leaking the patch target release date weeks ahead of time, always published on major sites. We knew well in advance when patch 3.3 was going to drop; nearly everyone who visits any WoW site other than the official one knew.
The other result of the lack of external communication is the frenzied excitement that builds around any information Blizzard gives. This is great for their marketing campaigns, but fails when they let the lack of information drag on for so long that people are compelled to leak things. The fruit dangling in-front of those who publish leaks becomes, eventually, too great to resist; serviced by people who don't believe Blizzard is doing a good enough job at keeping the community informed. The lack of information, and the build-up to the release of that information, ultimately backfires on Blizzard.
Fourth, and perhaps most importantly, it's time that Blizzard stop burying their heads in the sand over leaks and unreleased information. It doesn't work to deny the situation. One solution would be to at least say, "Yes, it's out there. But we don't want to talk about it." An even better approach would be to start talking about what's done and not done yet in the leaked info. (A blanket answer of "it's all not done" doesn't work. While everything might be changed slightly, people shouldn't be incorrectly led to hope that the Super Awesome Super Shot XL10 may be buffed substantially when there's actually no chance of it.)
I do want to take a second to note here that in minor ways, Blizzard has acknowledged the leaks exist -- but they still won't address them any farther than to repeat the same tired legal line ("We don't discuss anything under an NDA"). They have reiterated there are only certain things people can talk about (with regards to published Cataclysm content) on their forums, and those things are only items which they've (the blues) have posted either on the forums or on the official site. This level of content distinction, is well, silly.
I write this editorial on leaks and communication not to bash Blizzard or to undermine the game and the community that surrounds it; I'm writing this to clarify the system of politics that goes into something like this. If this subject matter were better understood by the entire community, then we'd all be better off.
Filed under: Analysis / Opinion, Cataclysm







Reader Comments (Page 1 of 8)
Moonkinmaniac May 7th 2010 2:04PM
I have a feeling at least some of this leak was allowed. The game has reaches a bit of a lull and it helps to create excitement and keep people playing.
CrimsonEyedDeath May 7th 2010 2:13PM
Even if it isn't, it's good for them, in a way. Not that there was a massive leak, but that millions of people are so bloody excited for the next bit of WoW that they're F5ing sites like WoW.com/MMO-champion/etc over and over and over again. I'm pretty sure there's at least some people who have went out and pre-ordered Cata off these screens/info alone.
If nothing else, this proves there's still alot of people interested in WoW in general, and Cata in specific, but we already knew this.
Now, personally, a leak this big, I start to wonder. Maybe it was intended, because, as someone said, this isn't a leak, it's a gaping hole.
Fletch May 7th 2010 2:28PM
I completely agree. I think Blizzard knows that there will be a continual leak of information - indeed I think their marketing strategy relies on it to create a buzz before the game's release. Although it's completely unprovavble, I'm willing to bet that if there were no leaks the initial sales of the game would be far lower than if there is a steady trickle of 'secret game information' coming out to pique peoples' interest.
cygnus May 7th 2010 2:33PM
I think a "friend & family" candidate was a 14 yo boy...
Drakkenfyre May 7th 2010 2:41PM
The whole floodgate opening up on MMO-Champion.com makes me think some of it was allowed, too.
The sheer amount of images he put up, without a public peep from Blizzard, makes me think they let him leak some. When the Wrath of the Lich King Wiki went up and was leaking stuff, they got a C&D after awhile, but eventually went back up.
It just seems like this much at once, some of it was allowed.
Maybe they see the leak as good advertising? Officially deny it, delete all references on the forums, but don't actively try to shut down the leaks yet. Then again, I don't think if they were doing that, they would permanently ban people from the forums.
Adam Holisky May 7th 2010 2:41PM
When I put on my Fox Mulder hat on, yes, this could have been a coordinated leak with Blizzard's approval.
However, I highly *highly* doubt that's the case. In fact, I'm 99.99999999% sure. I'm not going to go into why I'm sure, since that'd violate the trust of a lot of people have put into me, but trust me here... I really don't think the leaks were coordinated by Blizzard.
snowleopard233 May 7th 2010 3:06PM
I almost feel as if there’s not anything that “spoilerific” about these images. Although, I agree they shouldn’t have been leaked and can understand Blizzard’s agitation, I don’t think the end results will be that negative. There’s a lot of information here for sure, but I don’t feel there’s much that gives away any major plot points. We’re seeing the environments, we’re seeing the stage being set, but what we’re not seeing are the actors, those blizz is providing and the one’s we direct ourselves, and how these characters will create a story out of the scenery. It’s these details, spoilers like the one’s Boubille introduced before Cataclysm’s reveal that I was more afraid of.
jtrain May 7th 2010 3:24PM
@Adam H.
While you might be right that Blizzard didn't coordinate the leaks, I think it is safe to assume that Blizzard was and continues to be well aware that leaks will occur. We've seen this before with previous expansions and patches, and Blizzard is not naive. The only way to truly guarantee that information will not be leaked is to keep the Alpha 100% internal. Only when they're comfortable with the possibility of leaks would they then release the client to any non-Blizzard employees.
Blizzard might not have blessed the leaks, but there's no way that the Alpha makes it to the Friends & Family stage without Blizzard accepting the reality that some, if not all of the Alpha build would make it's way onto the Internet.
Ethan May 7th 2010 3:43PM
I think the tinfoil hat is on just a little tight when you say that this was a coordinated, intentional leak.
By putting this much stuff into the hands of the public (even though it's a relatively small public) you're more or less guaranteeing that someone, somewhere is going to leak it. I'm sure they're just aware of that as we are.
Hollow Leviathan May 7th 2010 3:57PM
In the interest of external communication and being forthright with wow insider fans, can you put a release date on when the private information you have relating to why you think this was not a deliberate action will no longer be sensitive and you can tell us publicly?
Irem May 7th 2010 4:05PM
I don't think it was coordinated, but I'm guessing that they probably knew that it would get leaked one way or another, and that they wouldn't be able to stop it once it got out, and that might be one reason they waited so long to fire up the alpha. Keep in mind that MMO-Champion only leaked their huge amount of screenshots after the alpha client hit the internet; before that, Boub was very careful not to break the NDA, even saying that he'd be checking to see what information he could release. Not touching MMO-Champion for leaking stuff is the best case scenario after the client's out, because Boub's screenshots are very high quality, they make the content look really exciting and impressive, and the majority of people casually looking for leaked alpha stuff will see only those. So I don't think Blizzard planned to leak anything, but I'm pretty sure they had some plans for making the best of a bad situation.
Snuzzle May 7th 2010 7:44PM
Based on events, I can infer that this is what happened.
1. Somehow a screenshot of Deathwing got on Boub's server (I don't know the details on that) and it got leaked.
2. Boub then was very angry that this got leaked, and he's never really cared much about leaks before.
3. Boub has posted that he was under NDA.
From this we can infer that he was, in fact, in the Alpha and was furious that the leaked DW screenshot risked him getting kicked out.
1. Boub has now posted massive, massive spoilers on his website.
From this, I infer that he DID in fact get thrown out of the Alpha, or was on the brink of it, and so he is saying to hell with the NDA, might as well be hanged for a flood as a drop.
Chris Anthony May 8th 2010 12:04PM
@Hollow Leviathan, keep in mind that revealing an "expiration date" for the secrecy would itself be leaking important information.
(cutaia) May 7th 2010 2:07PM
My question is whether or not the "friends and family" part of the alpha indicates that it really is for friends and family, or if it's just a cute name.
Because if it's truly friends and family who are violating the trust they were given...that's pretty douchy.
Jay May 7th 2010 2:33PM
Well most of the "leaks" came from Boubouille, who actually followed the NDA this time around. The only reason he posted images was because Blizzard allowed it, before May 6th he was deleting leaked content posted on MMO-C.
I can understand having an NDA on pre-alpha stuff because it in no way represents the final content, however Blizzard know this is great publicity.
These "leaks" of information have convinced me to buy Cataclysm.
kia May 7th 2010 4:44PM
Boubouille hasn't signed an NDA. He's not in the Alpha. Pretty sure owners of Blizzard fan sites (official or otherwise) don't get Alpha invites as a matter of principle.
Irem May 7th 2010 4:58PM
"The Alpha is protected by a Non-disclosure agreement, which basically means that anything I could post could get me sued. I'm not saying it will happen, Blizzard has been fairly forgiving with everything posted on the site in this past but I think you will understand that I cannot just post everything I find without checking a few things first."
Boub is in fact under the NDA, and he's alluded to the fact that he's in the alpha.
Roddythew May 7th 2010 7:11PM
I agree it's douchy. But I'm wondering, will Blizz REALLY prosecute its 'Friends and Family' for break their contract (non-disclosure agreement) with it? If not, how do will they keep leaks from happening in the future?
Vankay May 8th 2010 1:11AM
Im very curious if the perpetrators will be persecuted, Someone in the F&F leaked at least the direction of the client. mmm
Tom_inf_realm May 7th 2010 2:09PM
A leak of this size of something under an NDA has clearly been allowed, up to a certain extent, though releasing as many models and the client for sandboxing in is a much more unlikely thing to have been intended.