Thanks
Thanks to everyone who participated in Blackout Monday. It made quite a bit of stir in the gaming press, and shows our solidarity and commitment to the truth. The next step in the protest to GameSpot will be one that directly targets the management at CNET responsible for their poor decision to force the editors to work in an environment of fear.
More details will be forthcoming two days from now - we want to give CNET the opportunity to come genuinely clean and admit their wrong doing. Though we fully believe they will continue to deny allegations, and never truly address why the Kane & Lynch video review was pulled (other than vaguely saying things about "tone") or why the written review was rewritten. Suffice it to say, changing a review who's only "controversial" side was that Eidos didn't like it requires more than legalese, it requires a genuine confession.
See you all as soon as the next step is ready to go - I want us to have as professional and organized a next step as we can, something that the mainstream press can get behind, and help the story get out.
Update - Blackout Monday
Attention.
Please do not go on GameSpot, GameFAQs, CNET, Download.com, TV.com, et cetera... do not go on ANY CNET site. Logout and DO NOT GO ON AT ALL from 12am EST on Monday (that's midnight tonight) until 12am EST on Tuesday. Don't come on the site, don't Google the site, don't click on a link to the site - don't do ANYTHING that generates a page view, search engine hit, or *anything*
A lot of Gamespotter's more prominant posters will be taking this action to show solidarity with the staff (and Jeff) who have to fear their jobs being lost if they speak their mind. So for their inability to speak on this issue *we'll show CNET our silence*.
This issue is bigger than you, it's bigger than me - it's bigger than GameSpot. This is about big business being able to use *buy* public opinion. Rather than live in a world where the media is controlled entirely by those with the most money, I want to live in a world where gamers who are living for their hobby (these guys truly work because of their passion for gaming, not the paycheck) can say what they truly feel about a game.
So let's do the right thing and show solidarity with Jeff Gerstmann - if he can't go to work on Monday at GameSpot then neither will we.
For the Greater Good - Not the Greater Stupidity
I'll volunteer some wisdom on this, and it's worth noting. First - let's keep the "Jeff Talk" over in the appropriate thread. The reason for this is two-fold. First, it collects together the concerns, complaints, information and good-byes into one large lump sum that has a far greater impact than any splattered grouping of dozens of other postings could. And secondly, it reduced the moderation load (locking) that has to occur, leaving the mods free to discuss the incident.
Now on to the issues:
1. The Credibility of GS Scores
GS Scores, regardless of the validity of the Kane & Lynch claims, are being called into question. Rather than go through a laundry list of scores, or whining, I think we simply need to have some patience, and (going forward) find out as much as we can. We need to figure out what ulterior motives might have played into things like the review score overhaul. But, more importantly, we need *facts* not speculation, not cross-site comparison, not "well I feel". Remember, a review score is just a reviewer's opinion. Until we know if opinions were bought, we need to move forward calmly.
We've got a lot of titles and games for all systems to address - and of course there is the grander question of CNET. This will be something we need as much information as possible one. Above all us, we must promote quality information - as individuals outside of the company we are at an information deficit - one we must correct.
2. Handling AAAs
Whether or not the incident is true, the faith in GS scores, and AAAs by GS rule has been shaken. I propose we wait one week and then hold an official vote on what (if any) we will use for this determinant. It may be best, for the time being, to simply let scores go.
3. Moving Forward
Finally, we need a moratorium on fakeboys, idiocy, and general infighting in System Wars. This is a time for us to unite and move forward, to say "there's a bigger issue going on with GS and our systems". If this is a wake-up call in gaming journalism, so be it, but I propose we take a few days from thinking about the war, and start taking a serious look at where PR, Journalism, and hype has gotten us, and how it is *infecting System Wars*.
4. This is Partially Our Fault
System Wars (not just on this site) is why Eidos would want to buy reviews in the first place (if they did such a thing). Publishers tie salaries for some game developers to review scores. Why? Because review scores have been shown to directly impact sales. We need to address how our *own focus* on "official review scores" may be corrupting the industry, and journalism. This is something system wars will have to address in the future.
We need to address how we are buying into PR, Marketing, and Sales Data - how (by tying our a part of our identity to a companies success) we have allowed ourselves to be targeted. Our eagerness for "ownage" creates a market ripe for deceit - how can we prevent companies from believing the media can be used in this way? How do we punish unethical businesses practices - not just with Kane & Lynch, but also with games we might personally enjoy?
5. Maturity
This is our time to decide how we approach things, and it may be time to do the mature thing, act like adults, and start thinking. Many of you are younger, this might be the first time you've been *bluntly asked* to do the right thing. So do it. GameSpot and its credibility may never recover from the events of the past twenth-four hours... but as a community, as posters, we are greater than any one site, any one event. We are ultimately the driving force of this industry - and we need to show it where to go.
-
I have a great faith in each of you, let's plan how we move forward, what we address, and where we go from here as a community.
Log in to comment