Archive for the ‘transparency’ Tag
A few months back Scott Rosenberg and I filed our final report to the Knight Foundation on the first two years of MediaBugs. Here’s the full top-line summary from it, detailing how our various wins and losses with the project looked from our perspective. (And for much more on our work, check out our various commentary and analysis collected on the MediaBugs blog.)
At the end of 2011 MediaBugs is pivoting from a funded project to a volunteer effort. We’ve racked up some considerable successes and some notable failures. Here’s a recap covering the full two years of project funding:
* We built and successfully launched first a Bay Area-based and then a national site for publicly reporting errors in news coverage. These projects represented a public demonstration of how a transparent, neutral, public process for mediating the conversation between journalists and the public can work.
* We surveyed correction practices at media outlets both in our original Bay Area community and then nationally and built a public database of this information.
*We built and maintained a Twitter account with approximately 500 followers to spread awareness of both MediaBugs itself and other issues surrounding corrections practices.
* We maintained our own MediaBugs blog and contributed frequently to the MediaShift Idea Lab blog, where our posts were selected by the 2011 Mirror Awards as a finalist.
* We led a campaign to improve those correction practices in the form of the Report an Error Alliance, collaborating with Craig Silverman to promote the idea that every story page should have a button dedicated to inviting readers to report the mistakes they find. The practice has gained some momentum, with adoption at high-traffic websites like the Washington Post and the Huffington Post.
* We handled 158 error reports with the two largest outcomes being closed: corrected (59) and closed: unresolved (68). Those results included corrections across a range of major media including The New York Times, Wall Street Journal, Washington Post, USA Today, Fox News, CNN, National Public Radio, CBS News, the Associated Press, Reuters, Yahoo News, TechCrunch, and others.
* We took one high-profile error report involving “American Taliban” John Walker Lindh, KQED, and the New York Times, and used it as a kind of teachable moment to publicize some of the problems with existing corrections practices as they collide with digital-era realities. Our extended effort resulted in the Times correcting a story that the subject (through his father) had failed to get corrected for nearly a decade. The full write-up of this story was published on The Atlantic’s website in July, 2011.
* Our surveys of correction practices and related public commentary led many news outlets to revamp and improve their procedures. And many of the specific error-report interactions that led to corrections helped shed light on formerly closed processes in newsrooms, leaving a public record of the interaction between members of the public who brought complaints and journalists who responded to them.
* We partnered with other organizations, including NewsTrust and the Washington News Council, on efforts to correct inaccuracies in news coverage and establish regional MediaBugs organizations. Our software platform became the basis for Carl Malamud’s Legal Bug Tracker project.
Our single biggest failure was our inability to persuade any media outlet with a significant profile or wide readership to adopt our service and install our widget on their pages. This limited our reach and made it difficult to spread our ideas. Users had to know about our service already in order to use it, instead of simply finding it in the course of their media consumption.
Our efforts to solve this problem — outreach to friends and colleagues in media outlets; public and private overtures to editors, newsroom managers, and website producers; back-to-the-drawing-board rethinks and revamps of our product and service — occupied much of our time and energy through the two years of the Knight grant.
We did find some success in getting MediaBugs adopted by smaller outlets, local news sites and specialty blogs. In general, it seemed that the people who chose to work with us were those who least needed the service; they were already paying close attention to feedback from their readership. The larger institutions that have the greatest volume of user complaints and the least efficient customer feedback loops were the least likely to take advantage of MediaBugs.
We identified a number of obstacles that stood in our way:
* Large news organizations and their leaders remain unwilling even to consider handing any role in the corrections process to a third party.
* Most newsroom leaders do not believe they have an accuracy problem that needs to be solved. Some feel their existing corrections process is sufficient; others recognize they have a problem with making errors and not correcting them, but do not connect that problem with the decline in public trust in media, which they instead attribute to partisan emotion.
Our other major failure was that we never gathered the sort of active community of error reporters that we hoped to foster. Our efforts included outreach to journalism schools, promotion of MediaBugs at in-person events and industry gatherings (like Hacks and Hackers and SPJ meetups), and postings at established online community sites whose participants might embrace the MediaBugs concept. But our rate of participation and bug-filing remained disappointing.
One explanation we reluctantly came to consider that we hadn’t originally expected: Much of the public sees media-outlet accuracy failures as “not our problem.” The journalists are messing up, they believe, and it’s the journalists’ job to fix things.
A final failure is that we have not, to date, made as much progress as we hoped in transforming journalists’ way of thinking about corrections. We imagined that public demonstration of a more flexible view of errors and corrections would encourage a less secretive, less guilty-minded, more accepting stance in newsrooms. But two years after MediaBugs’ founding, getting news organizations to admit and fix their mistakes in most cases still demands hard work, persistence and often some inside knowledge. Most of the time, it still feels like pushing a boulder up a hill. This needs to change, for the good of the profession and the health of our communities, and MediaBugs intends to keep working on it.
Why so quiet here on the blog the last couple months? As many of you know, in September I started a new gig at Mother Jones. That’s keeping me pretty busy these days, but I’ll continue to post here from time to time. You can also follow my work over there. Some recent pieces include: my further reporting on the strangely inconsistent accounts of how the US military killed Osama bin Laden; how the hacks behind Andrew Breitbart’s Big Government website got caught making a big blunder on climate change and wouldn’t cop to it; and how Breitbart and other right-wingers apparently became obsessed with raunchy jokes about Occupy Wall Street. I also edited and produced multimedia for a major investigative project about Texas criminal justice gone horribly wrong. The story, “No Country for Innocent Men,” was written by the great Beth Schwartzapfel, and you should go read it now. (Also watch the video, read the prisoners’ letters, and peruse the interactive map.) It is emotionally searing and deeply informative.
September also marked the end of the two-year Knight News Challenge grant that funded MediaBugs. The error-reporting service remains fully operational; my project partner Scott Rosenberg (who is now the executive editor of Grist) and I are continuing to run it on a volunteer basis. We had a number of great successes with MediaBugs in the first two years of the project — as well as some frustrations and failures. In January we’ll detail those in a report that we’re planning to publish on the MediaBugs blog. Transparency is a cornerstone of the project, and we believe there is value, both for our media colleagues and the news-consuming public, in sharing what we’ve learned. I’ll also re-post the report here.
As always, thanks for reading — and more to come soon, both here and over at MoJo!
[This post has been revised and expanded several times since initial publication; see updates below.]
You don’t have to be a conspiracy theorist to be still scratching your head about the end of Osama bin Laden. Between the Obama administration and major US media, the story of the Navy SEALs’ mission in Abbottabad has never seemed quite straight, tilting toward the political or fantastical more than the cohesive. In some respects that’s unsurprising for one of the most important and highly classified military missions in modern memory — one whose outcome, many would argue, is all that really matters. But as America prepares to reflect on the tenth anniversary of 9/11, it’s worth considering how the tales have been told, and where history begins to bleed into mythology. After several months of revised accounts and inside scoops, we still have a conspicuously muddled picture of bin Laden’s killing.
Lots of praise flowed earlier this month for Nicholas Schmidle’s riveting account in the New Yorker of the SEALs’ raid on bin Laden’s compound. It added many vivid details to what was publicly known about the killing of America’s arch-nemesis that fateful morning in early May. But Schmidle’s exquisitely crafted reconstruction also contradicted previous reporting elsewhere, and sparked some intriguing questions of its own.
It underscored what we still don’t really know about the operation. Schmidle’s depiction of the tense scene in the White House Situation Room, as President Obama and his top advisers monitored the action with the help of a military drone, included a notable refutation. The SEALs converged at the ground floor of bin Laden’s house and began to enter, Schmidle reported, but:
What happened next is not precisely clear. “I can tell you that there was a time period of almost twenty to twenty-five minutes where we really didn’t know just exactly what was going on,” [CIA chief Leon] Panetta said later, on “PBS NewsHour.” Until this moment, the operation had been monitored by dozens of defense, intelligence, and Administration officials watching the drone’s video feed. The SEALs were not wearing helmet cams, contrary to a widely cited report by CBS.
Schmidle was referring to a May 12 story by veteran CBS News national security correspondent David Martin headlined, “SEAL helmet cams recorded entire bin Laden raid.”
The contradiction has big implications. Martin’s own story was in part a response to the famously mutating account from the Obama White House in the days following the mission. The administration had attributed its multiple revisions to “the fog of war” after backtracking from claims that bin Laden had engaged the SEALs in a firefight and used his wife as a human shield. Martin’s piece stated he was putting forth “a new picture of what really happened” in Abbottabad; he reported that “the 40 minutes it took to kill bin Laden and scoop his archives into garbage bags were all recorded by tiny helmet cameras worn by each of the 25 SEALs. Officials reviewing those videos are still reconstructing a more accurate version of what happened.”
Such footage obviously could go a long way toward a precise account. According to Schmidle’s New Yorker piece, though, it doesn’t exist.
There are other glaring discrepancies between the New Yorker and CBS News reports concerning the climax of the raid. In Schmidle’s version, the encounter involved two of bin Laden’s wives, and one SEAL firing the kill shots:
The Americans hurried toward the bedroom door. The first SEAL pushed it open. Two of bin Laden’s wives had placed themselves in front of him. Amal al-Fatah, bin Laden’s fifth wife, was screaming in Arabic. She motioned as if she were going to charge; the SEAL lowered his sights and shot her once, in the calf. Fearing that one or both women were wearing suicide jackets, he stepped forward, wrapped them in a bear hug, and drove them aside….
A second SEAL stepped into the room and trained the infrared laser of his M4 on bin Laden’s chest. The Al Qaeda chief, who was wearing a tan shalwar kameez and a prayer cap on his head, froze; he was unarmed…. Nine years, seven months, and twenty days after September 11th, an American was a trigger pull from ending bin Laden’s life. The first round, a 5.56-mm. bullet, struck bin Laden in the chest. As he fell backward, the SEAL fired a second round into his head, just above his left eye.
But in Martin’s version, the encounter involved bin Laden’s “daughters” as well as one of his wives — and not one, but two SEALs firing the kill shots:
The SEALs first saw bin Laden when he came out on the third floor landing. They fired, but missed. He retreated to his bedroom, and the first SEAL through the door grabbed bin Laden’s daughters and pulled them aside.
When the second SEAL entered, bin Laden’s wife rushed forward at him — or perhaps was pushed by bin Laden. The SEAL shoved her aside and shot bin Laden in the chest. A third seal shot him in the head.
What’s going on here? Martin’s piece for CBS aired nearly two weeks after the raid; presumably the US government had its story straight by then. (The Guardian’s roundup of White House revisions linked above was published on May 4.) Martin provides scant information about his sourcing. If his piece has turned out to contain inaccuracies, to date CBS News has given no indication.
It is also possible that Schmidle’s piece contains inaccuracies, although it is more deeply reported and goes further in describing its sources. They include Obama’s chief counterterrorism adviser John O. Brennan, deputy national security adviser Ben Rhodes, and perhaps most significantly, “a special-operations officer deeply familiar with the bin Laden raid.”
Still, Schmidle wasn’t able to interview any of the Navy SEALs directly involved in the mission, despite that his piece seemed to suggest he had. Instead, Schmidle told the Washington Post’s Paul Farhi, he relied on the accounts of others who had debriefed the men.
Schmidle wrote conspicuously of the SEALs’ perspective during the raid: “None of them had any previous knowledge of the house’s floor plan, and they were further jostled by the awareness that they were possibly minutes away from ending the costliest manhunt in American history; as a result, some of their recollections — on which this account is based — may be imprecise and, thus, subject to dispute.”
From fraught US-Pakistan relations to conspiracy theories to partisan politics, it’s an understatement to say that there is keen interest in knowing exactly how the killing of bin Laden went down. Faulty reporting may be to blame for standing in the way. Alternatively, the mind doesn’t require much bending to imagine why military, CIA or White House officials might have been happy at various turns to help muddle the story. A certain degree of imprecision or misdirection can serve the side of secrecy. Perhaps at a time when the White House declined, amid much clamor, to release photos of bin Laden’s corpse, it was useful to let the world know that it also had video footage of the whole operation. Perhaps at some later point it was useful to quash the idea that the US government had lots of raw footage with which it might address questions about the circumstances and legality of bin Laden’s killing.
Whatever the case, one of two stories from major American media outlets is flat-out wrong on a significant piece of information about the raid. (As well as on some other details, it seems.) It may be that a precise account of the historic military mission will elude us for a long time, just as its target so famously did.
How many SEALs? (Update, Aug. 4)
Looking back over the CBS News piece again, I spotted another discrepancy: Martin reported that 25 SEALs stormed bin Laden’s compound; Schmidle’s New Yorker piece says there were 23 SEALs directly in on the raid. (Plus a Pakistani-American translator and a now legendary Belgian Malinois.)
Also, it’s worth noting how central the helmet cam information was to Martin’s story; the video version of it opened with a “CBS news animation” showing them:
I’ve also now filed an error report about this at MediaBugs, seeking a response from CBS News. I don’t have enough information to know whether their story is inaccurate, but it seems fair to say that the overall picture here suggests the onus is on CBS to corroborate their story.
Lack of disclosure (Update 2, Aug. 4)
In a guest post at Registan.net, Georgetown professor C. Christine Fair raises some provocative questions about Schmidle’s New Yorker piece, including about its sourcing. She is not the only one rebuking the magazine for failing to disclose clearly that Schmidle did not talk to any of the SEALs who raided the bin Laden compound. (That lack of disclosure apparently prompted an error and correction on NPR’s “Morning Edition.”) Fair wonders about how certain details in the story, and the fact that Schmidle’s father is the deputy commander of the US Cyber Command, might play across the Muslim world. Though I don’t necessarily share her conclusions, the post is interesting and worth a read.
“An administration puff piece” (Update 3, Aug. 10)
Marcy Wheeler has a rundown on Schmidle’s sourcing. She suggests that Obama senior advisers Brennan and Rhodes may have served as anonymous sources for the piece as well as named ones. (Not an uncommon practice in the journalism field, in my experience.) Thus, she argues, Schmidle’s piece deserves greater scrutiny in light of the “war on leaks” conducted under Obama. “This story is so thinly veiled an administration puff piece,” Wheeler says, “it ought to attract as much attention for the sheer hypocrisy about secrecy it demonstrates as it will for the heroism such hypocrisy attempts to portray.”
A Hollywood conspiracy (Update 4, Aug. 11)
Rep. Peter King, the Republican chairman of the House Homeland Security Committee, has called for an investigation into alleged collaboration between the Obama administration and filmmakers Kathryn Bigelow and Mark Boal (of “The Hurt Locker” fame) for a forthcoming movie about the bin Laden takedown. Reportedly due for release in October 2012, just before the next presidential election, the movie project “belies a desire of transparency in favor of a cinematographic view of history,” according to King. The White House says King’s take is “ridiculous.” The story here seems to be opposition party politics layered on top of presidential politics layered on top of a Hollywood production — with the finer facts of bin Laden’s demise buried somewhere beneath.
Seeking clarification (Update 5, Aug. 15)
I’ve reached out to Nicholas Schmidle by email asking if he can offer any additional information regarding the helmet cam issue. (His New Yorker piece says nothing about his sourcing on that particular point.) I’ve also contacted CBS News about it and am in the process of looking for a more direct way to reach David Martin.
More details that don’t add up (Update 6, Aug. 26)
For more on this story, read my piece over at Mother Jones, which includes further examples of conflicting details from news reports on the bin Laden mission.
[Post updated below through May 10.]
In my view there’s a clear and compelling reason why the United States should release an image of Osama bin Laden’s corpse. It has little to do with nutty conspiracy theories, which were a consideration in the White House decision not to “spike the football.” For most of the world already, the fact of bin Laden’s killing is indeed unimpeachable. (One reason why President Obama deserves huge credit for what many view as his very “gutsy” call on the Navy Seals operation.) Even if bin Laden’s body had been displayed for a month in Mecca prior to disposal, there would still be crazies in the Arab world and beyond convinced of some grand, evil scheme. (“A fraudulent corpse delivered by the Mossad, CIA and George Soros!” Etc.)
More importantly the White House is wary of inflaming Muslim opinion against the U.S. But from Abu Ghraib to Guantanamo to the Koran-burning pastor in Florida to U.S. military atrocities in Afghanistan, the case of inflammation is already chronic. It’s a problem not easily controlled, let alone alleviated. I’m not sure I see how visual evidence of bin Laden’s death, even if pretty gruesome, adds significantly to it.
Proof isn’t the key point. (Nor is jingoism.) The reason to release the photo is the tremendous value of destroying, with vivid finality, bin Laden’s potent mythological image. Yes, the devotees of his jihad will promote the whole martyr thing. But they’re already doing that anyway.
Those who’ve studied bin Laden’s journey know how incredibly important his carefully tended cult of personality has been to his cause. Lawrence Wright documented this exhaustively in his masterful tome, The Looming Tower: Al Qaeda and the Road to 9/11. In the decade since 9/11, bin Laden’s successful evasion of the mightiest military in the world fed his symbolic power and the inspiration of his followers. It gave him a kind of metaphysical strength and credibility far greater than any cries of martyrdom now can. If his killing at the hands of the U.S. military was indeed a “decapitation” of Al Qaeda, then once that killing is in clear view bin Laden’s death cult also loses its heart.
No doubt a gruesome image would stir strong emotions around the world. But anger at the U.S. would be affected minimally and ephemerally, I think, discounting those already stewing in the radical margins. The narrative benefits of the publicity would be greater. Especially, as Steve Clemons suggests, if the White House were to release images simultaneously of bin Laden’s “respectful” burial at sea.
UPDATED 5/5/11: An opinion piece today from the International Herald Tribune, “The Death of an Icon,” goes to the heart of my thinking on this issue. “Osama bin Laden, the visual icon of terrorism in our fear-driven age, is gone,” writes Columbia history professor Richard Bulliet. “No one can replace him.”
He explains in detail why bin Laden “was unquestionably the master recruiter” for Al Qaeda:
Compared with the two-dozen jihadist videotapes I analyzed in connection with police investigations in 2002-2003, Bin Laden’s propaganda stands out. Not only does it present a plausible argument for jihad against the West, but his visual presence and calm voiceovers convey an aura of authority and leadership even though his name is never mentioned.
His screen presence also far outshadows that of other jihadist leaders. Where they are strident, or ranting, or dull, he is calm and articulate. Where they come across as one-note preachers or pedantic classroom teachers, he appears as a fully formed individual. Comfortable in the mosque, on the battlefield, at the training camp, or in a poetry recital.
One cannot mourn the death of a man who planned or inspired so many atrocities. But we should recognize that his bigger-than-life iconic presence was the heart and soul of jihadist Islam.
Read the whole piece — essential analysis on the meaning and impact of bin Laden’s end.
Also see Deborah Copaken Cogan, who suggests that “to sanitize photos is to distort history.”
UPDATED 5/10/11: The Associated Press is pursuing the bin Laden images with a Freedom of Information Act request. The AP cites Obama’s campaign vow to make his administration “the most transparent government in U.S. history” and points to the muddled narrative surrounding bin Laden’s killing, which has been revised multiple times by the White House. Says AP senior editor Michael Oreskes about the visual evidence of bin Laden’s death: “This information is important for the historical record.”
Last Wednesday, USA Today editor Doug Stanglin reported about the Associated Press’s hugely embarrassing misfire-of-a-story on General Electric. In a blog post headlined “AP falls for prank report that GE is giving back a $3.2B tax refund,” Stanglin quoted from AP’s correction, included the full text of the retracted AP story on GE, and cited a report from Reuters about the activists behind the hoax.
It was a thorough rundown except for one thing: USA Today had also fallen for the prank report. The fact that it ran the bogus story from AP, and later removed it from USAToday.com, did not make it into Stanglin’s blog post. Why not?
Many news outlets run wire stories using an automated feed of some kind. Given the speed and volume of the content it’s easy to see how mistakes or problems could be missed — and whether news sites should be responsible for corrections to erroneous wire stories they’ve run has been an open question, as we noted in this recent error report at MediaBugs.
But when a news outlet makes the effort to report on another outlet’s high-profile bungle — and fails to mention its own participation — readers are bound to wonder why.
If you searched for the bogus GE tax story on Google News on Wednesday, you would have seen that USA Today ran with it:
Many people quickly took notice of USA Today’s publication of the story, including the pranksters themselves. But later on Wednesday if you clicked on the link to that story, you arrived on a USA Today page simply telling you that it had been removed:
In other words, between the link to the retracted story (later on filled in with AP’s correction) and Stanglin’s blog post, USA Today essentially provided no record on its site that it played a part in spreading some majorly wrong “news.” Nor was there any mention on USA Today’s corrections page, despite the high-profile nature of the mistake, which had real consequences. (GE’s stock price dropped significantly on the fake news.)
If the AP’s blunder had been headed for USA Today’s print pages, it would have been caught and not published — but even in the unlikely event that it had been published, you can be sure the paper would have run a correction notice in a subsequent edition. Online publishing makes it easier to cause embarrassing errors to disappear, but it doesn’t remove any of a publisher’s responsibility to own up to and correct them.
MediaBugs reached out by email to both Stanglin and standards editor Brent Jones to find out why USA Today handled things the way they did. Both responded quickly and cordially, with a definitive explanation on Friday morning from Jones:
USA TODAY’s newsroom practice is to be forthright and transparent when setting the record straight. We responded to reader inquiries and published a correction on Twitter, but we should have included that we published the AP’s story when reporting on the GE tax hoax. To clarify with our readers, website editors have since updated our blog posting, posted a note on our corrections/clarifications blog and the AP’s corrected report.
It’s good that USA Today had put the word out on Twitter, and we applaud them for addressing the problem thoroughly on their site pages in response to our inquiry. (You can now see those updates here, here, and here.) Also worth noting is that USA Today’s accessibility and corrections practices put them at the front of the pack of U.S. media. Even so, in this case they needed external prodding to do the right thing.
Perhaps the online medium makes it easier to stumble in this way. It’s simple enough to unpublish something and just move on — and far too many news sites still lack a clear process for tracking and rectifying their mistakes. There may also be an increasing tendency, navigating today’s ephemeral sea of news, to shrug off responsibility for nonproprietary content. Wire stories, blog posts and tweets seem at once to come from everywhere and nowhere. That’s precisely why this case is instructive.
It’s simply not possible to walk away from the kind of goof USA Today indirectly made. Social media, search engines and other tools will capture it. As more and more content is syndicated, aggregated or borrowed (with or without permission), newsrooms may feel they are less responsible for its accuracy. But in an era of deep distrust of the media, the opposite has to be true. When a news site chooses to repeat someone else’s report it shoulders new accountability along with it — including a duty to correct errors, thoroughly and forthrightly, before they get compounded further.
[Cross-posted from the MediaBugs blog.]
Back in late February, Fox News columnist Juan Williams wrote a scathing piece about racial prejudice in the media. Exhibit A was the Washington Post’s coverage of a poll showing that African Americans and Latinos are optimistic about the economy. The Post, Williams charged, had “buried” this good news because it didn’t fit with the bleak racial stereotypes typically found on the front pages of “the big, white press.”
Since it turns out that the Post actually had splashed the upbeat poll story all over its Sunday front page and its website, the “entire premise” of Williams’ column, as a reader reported at MediaBugs, was flat-out wrong.
At MediaBugs we did what we do in this situation, which is to try to get a response from the media outlet behind the piece in question. Yet, despite multiple attempts on our part to alert Williams and Fox News to the problem, they failed to respond or correct the blunder for weeks.
On Tuesday, Fox finally posted an editor’s note on the piece:
EDITOR’S NOTE: The results of the poll referred to in this article were in fact reported on the front page of the Feb. 20 editions of the Washington Post. Mr. Williams regrets the oversight to the Post, and maintains the study’s findings deserved more prominent coverage in other media outlets.
The good news here is that Williams and Fox finally took responsibility for the mistake. Bravo! We mean it.
Nonetheless, it’s just possible that Williams and Fox might someday make another mistake. And since MediaBugs has published a set of best practices for error reporting and corrections, we thought we would offer a few suggestions should they ever find themselves in this position again:
- Don’t wait a month and a half to fix an error, especially when it’s a flagrant one. If you can’t respond in short order, at least acknowledge inquiries on the matter and let folks know you’re looking into it.
- Try not to mince words. Call an error an “error” and a correction a “correction.” Readers can probably surmise the meaning of “Mr. Williams regrets the oversight to the Post.” But it’s classier not to downplay a mistake while you’re in mid-regret.
- Don’t use a correction to reiterate an argument. Williams certainly is free to wish that other outlets such as the New York Times had covered the Post poll — though, veteran that he is, he must know that most media companies rarely give big play to their competitor’s surveys. But when you’ve reported as fact something that hundreds of thousands of newspaper and online readers know to be false, your mea culpa is not the right place to declare “I was right anyway!” Write another column if you must.
- Give your audience a clear and easy way to alert you when you’ve gone astray. If your “Email Newsroom” link leads the public into a brick wall, and they’ll have to spend weeks chasing down other ways to try getting your attention, you can safely conclude that your status quo is ineffective.
A really good start, in fact, would be to publish any kind of corrections page and policy on your website.
[Cross-posted from the PBS MediaShift blog.]
Recently the Spanish-language site of Yahoo News reported that NASA had contracted with three companies to develop some truly incredible commercial aircraft. The future planes, Yahoo reported, could be available by 2025 and fly at 85 percent of the speed of light. Just imagine: You’d be able to jump aboard one of these suckers and zing from Vancouver to Capetown in, oh, about a fifteenth of a second. Now that’s newsworthy!
And perhaps it might even be possible — but it’s not true. As a MediaBugs user reported, NASA is in fact aiming for these future aircraft to reach 85 percent of the speed of sound. (Impressive in its own right, but nothing remotely approaching the speed of light.) Apparently somebody at Yahoo Noticias en Espanol had mistranslated the NASA press release from which the story was mostly drawn.
Even seemingly small errors in the news — in this case a single mistranslated word — can matter, and they should be corrected with care. The Yahoo story was fixed a day or two after the mediabug was posted — a positive outcome — although without any notice to the public that it was changed. [*See update below.] We don’t actually know how the error came to Yahoo’s attention; I couldn’t get any meaningful response from the company when I tried to let them know about it.
Which is quite difficult to do. Yahoo News has no corrections info or content of any kind, nor any real channel for contacting its editors or producers. (When I tried the “News Help Form,” found via a barely noticeable link in the page footer, I received a comically unhelpful “Escalation Notice,” followed a day later by an email from a customer service rep promising to “send this information to our editors if necessary.” By that point the article had already been fixed.)
As we revealed in an in-depth MediaBugs study published in November, many legacy print-news companies are still stumbling big-time when it comes to error reports and corrections online. Yahoo News, of course, can’t even plead about transitioning to digital in an era of dwindling resources; it is part of a pioneering technology company native to the two-way medium of the Web. So why isn’t it doing a better job with this stuff?
Part of the answer may be that Yahoo News primarily is an aggregation site, filled with wire service stories and links to reporting from other news organizations. But in July 2010 Yahoo launched The Upshot, a news blog with original content produced by a small handful of established reporters and editors. Yahoo News already commanded huge traffic, but now the company apparently was making a bid for greater news-media relevance (and, presumably, even more traffic). Its Twitter feed, followed by roughly 62,000 people, says that its “Tweets are hand-picked by the Y! News Team and 100% RSS feed free!” In other words, there are real people behind the curtain here.
Still, good luck reaching them. In addition to trying the “help” form and contact via Twitter, I emailed an Upshot editor, Chris Lehmann, to see about reporting the “speed of light” error. He responded quickly and cordially, telling me that he had no idea whom to contact about it, particularly since the error was on the Spanish-language site. I commented that correcting a substantive error without any notice to the public is bad form. (Yahoo News has company in this practice: The New York Times and Reuters recently were caught doing this too.) “On the U.S. news blogs,” Lehmann said with regard to substantive fixes, “we always append an update to note when we’ve corrected the text.”
The Upshot also stands out from the Yahoo News mother ship by providing on its main page a visible list of editorial staff and their contact info. “Keep us honest,” editor Andrew Golis wrote last July. “Email us, comment on our posts, let us know when we’ve made a mistake. When we agree with you, we’ll be fast and transparent about fixing it, apologizing and explaining.”
The rest of the Yahoo News operation should get onboard with that agenda if it wants the public to trust in its content, already an uphill battle for the news media in general.
Here’s a suggestion to the managers of Yahoo News for a good start: Join the Report an Error Alliance. Put that snazzy little red-and-black button on every news page. When it bleeps with reader feedback, have somebody around to respond in reasonably short order (light speed won’t be necessary!) and publish the results in a transparent, user-friendly way.
UPDATE, 11:30 a.m. PT: Things have since accelerated farther away from clarity: When I returned to the Yahoo News story page today to check for an update I discovered that the text has changed back to the erroneous version first published. Whereas the segments in question had been changed from “la velocidad de la luz” to “la velocidad del sonido” they are now back to the former.
My suspicion is that while the first change was in all likelihood made by a person, the reversion to the error is probably due to a system glitch whereby that fix was overwritten. Of course, this points back not so neatly to the crux here — we have no effective way to inform Yahoo News about the problem, let alone get a clear explanation from them.
[Ed. note: This post also appeared today on the MediaBugs blog.]
[Updates to this post, through Monday Dec. 13, follow below.]
When the “Afghan war logs” became public earlier this year, I focused on WikiLeaks from the standpoint of its huge impact on the media. The ongoing release of a quarter million State Department cables has since unleashed a torrent of hot debate about government secrecy and whether Julian Assange’s organization is a force for good or evil.
Like many others, I’ve marinated myself in related articles and commentary over the last week but remain ambivalent about some of the complex moral issues involved. I’ve also been pondering a question that seems noticeably absent from the discussion: Could it be that WikiLeaks is actually the best thing in a long time to afflict U.S. national security?
The cacophonous phenomenon on the world’s front pages has been a grand wake-up call — the rise of cyberwar is no longer a matter of theory. It’s here whether you believe Assange is an enemy or a hero. If it proves true that a low-level Army analyst was able to get his hands on such a colossal amount of sensitive documents, what does that say about Pentagon preparedness for the security challenges of the proliferating information age?
So far some contents of “cablegate” itself have informed our view of just how serious an issue this is. As the Times reported on Sunday, “repeated and often successful hacking attacks from China on the United States government, private enterprises and Western allies” have been taking place since as far back as 2002. One previously unreported attack “yielded more than 50 megabytes of e-mails and a complete list of user names and passwords from an American government agency.”
The China cables also show the fire with which WikiLeaks plays; you get the sense that if some of the redacted names were revealed, it could potentially be disastrous, both to individuals involved and to U.S. intelligence gathering.
It’s noteworthy that the Obama administration’s assessment of the damage from WikiLeaks has consistently been inconsistent. The latest round has Attorney General Eric Holder saying that “national security of the United States has been put at risk,” while Defense Secretary Robert Gates says that concerns about potential harm are “significantly overwrought” and that the disclosures will have a “fairly modest” impact on foreign policy. The mixed message would seem to suggest that the U.S. government yet lacks a coherent approach to safeguarding the nation’s information infrastructure.
In the later years of the Bush administration, the federal government began to prioritize cyberwar, a focus continued by the Obama administration. But today there are the troubling, all too familiar signs of unpreparedness, agency turf wars and legal muddle. The Pentagon’s Cyber Command seeks to expand its powers aggressively and is, not coincidentally, publicizing that fact now. According to the Washington Post, its general in charge recently testified to Congress that he could not adequately defend the country against cyber-attack because it “is not my mission to defend today the entire nation.” If an adversary attacked power grids, he said, a defensive effort would “rely heavily on commercial industry.” Former national intelligence director Dennis C. Blair warned, “This infuriating business about who’s in charge and who gets to call the shots is just making us muscle-bound.”
By some accounts the world hasn’t seen anything yet in terms of the looming dangers of cyberwar. An attack could cripple America, argues former counterterrorism chief Richard Clarke, striking everything from train routes and electrical grids to bank data and medical records.
WikiLeaks over the last few months, then, may have exposed U.S. government vulnerability in an alarmingly useful way, if one not much in line with Assange’s ideas about undermining state power. You can bet it has lit a serious fire under officials involved with the nation’s cybersecurity, who now must be working that much more intensively to plug any leaks in the ship of state and build up defenses against future attacks. They are, of course, likely toiling in secrecy. For now, anyway.
UPDATE: On the eve of his arrest in London, Assange publishes an article in The Australian: “Don’t shoot messenger for revealing uncomfortable truths.” He opens with a quote from Rupert Murdoch: “In the race between secrecy and truth, it seems inevitable that truth will always win.”
UPDATE 12/8/10: Hackers sympathetic to Assange and WikiLeaks have launched a series of cyberattacks in recent days, targeting MasterCard, PayPal and a Swiss bank. (Could Twitter be next?) The Guardian looks into the “shadowy group” allegedly behind the attacks:
A 22-year-old spokesman, who wished to be known only as “Coldblood”, told the Guardian that the group – which is about a thousand strong – is “quite a loose band of people who share the same kind of ideals” and wish to be a force for “chaotic good”.
There is no real command structure in the group, the London-based spokesman said, while most of its members are teenagers who are “trying to make an impact on what happens with the limited knowledge they have”. But others are parents, IT professionals and people who happen to have time – and resources – on their hands.
It’s really too bad that Stieg Larsson isn’t still around to witness all this.
UPDATE 12/13/10: The WikiLeaks saga itself continues to ratchet up the potential for cyberwar. With a secret grand jury in Virginia reportedly now considering criminal charges against Assange, a headline in today’s Daily Mail raises the specter of retribution for Assange’s potential extradition: “Britain on cyber warfare alert as Whitehall prepares for WikiLeaks revenge attacks on Government website, it reads. Apparently “bank details of taxpayers and benefits claimants” could be at risk.
Stateside, meanwhile, the Times’ Scott Shane reports movement on the cyberwar front: “Whether or not the Obama administration tries to prosecute those who disseminated the information, it is determined to use technology to preserve its secrets. The Defense Department is scaling back information sharing, which its leaders believe went too far after information hoarding was blamed for the failure to detect the Sept. 11 plot. The department has also stripped CD and DVD recorders from its computers; it is redesigning security systems to require two people, not one, to move large amounts of information from a classified computer to an unclassified one; and it is installing software to detect downloads of unusual size.”
*Post updated below with a response from a WSJ managing editor.
Just ahead of last week’s election the Wall Street Journal reported that “high-level Democrats” were calling for President Obama “to remake his inner circle or even fire top advisers” in the face of an imminent drubbing at the polls.
But an error report on MediaBugs flagged a conspicuous problem with the story: It contained no evidence supporting the claim in its headline and first paragraph. Not a single one of the eight people quoted in the piece called for Obama “to remake his inner circle” or “fire top advisers.” (Read the story here.)
Over the past week our MediaBugs team contacted the Journal five times seeking a response to the error report. We emailed a reporter, a managing editor and a general address designated for reporting errors to the newsroom. We also called the phone number listed with corrections info in the print edition. We haven’t received any response.
This isn’t the first time we’ve encountered a void when trying to reach the Journal about an error report. And while the previous instance involved a minor mistake, this one is more substantial.
It isn’t just that we think a reasonable error report deserves a response. It’s in the Journal’s best interest to provide one.
Surely more than one Journal reader wondered why there were no quotes to back up the story’s headline and premise. With no explanation from the newsroom, all we can do is speculate. It’s possible that the reporters spoke with “high-level Democrats” who said they wanted Obama to fire top advisers, but who would only say so off the record. (In which case the article might have explained that.) Or it’s possible an editor chose to punch up the opening and add a headline intended to attract maximum eyeballs. Maybe somebody at the Journal was eager to suggest a dramatic loss of confidence in Obama on the eve of a big election — after all, ever since Rupert Murdoch bought the paper, critics have been identifying a rightward slant in its news pages. (See, for example, The Atlantic, the New York Times, and many other sources.)
It’s also possible that the above explanations aren’t remotely accurate. We just don’t know.
Which, of course, is exactly the point. A Wall Street Journal reader raised a legitimate question; by failing to respond, the paper has left a void for its readers to fill with suspicion and surmise. (Journal readers may have noticed that no top advisers have departed the administration since the election; meanwhile, subsequent reports from Politico and NPR indicate that changes at the White House are likely to involve the “reshuffling of a relatively small cast of Obama insiders” and that “nobody expects an inrush of new blood.” Still, even the departure tomorrow of the entire White House staff would not answer the questions raised by the Journal story.)
When MediaBugs reaches out to newsroom managers about an error report, we explain that our aim is to help close the feedback loop, often inadequate, between the public and newsrooms. (Read our newly published national survey of news sites to see just how inadequate that feedback loop typically is.) We don’t tell editors whether they should run a clarification or correction — that remains up to them to decide and to articulate to the public.
In the pre-Internet age, it was easy for a news organization to control a conversation in the public view about its journalistic practices, or simply to ignore it altogether. Today, the conversation about journalism is everywhere; that’s the case whether or not a news organization chooses to engage with it. When it comes to championing accuracy, the best way forward is to be accessible, transparent and engaged with the public.
[Note: This post also appeared today on our MediaBugs blog.]
UPDATED Nov 12: The Wall Street Journal has finally responded, saying that it “fundamentally disagrees” with the error report posted on MediaBugs. You can read the Journal’s full response here. MediaBugs takes no position on specific bug reports; from my vantage as the project’s associate director I’ll say that we are glad to have the Journal’s response — a primary goal of ours is to connect the public with newsrooms on error reports and establish a useful record of the discussion that ensues.
In my personal opinion, as a blogger who sometimes writes about media, I’ll say that I find the Journal’s response totally lacking. It plays like bad kabuki, failing to address the actual problem raised by the bug report and further undermining the Journal’s credibility. I won’t spend time dissecting it here — because my project partner Scott Rosenberg has just done so over at Wordyard. “Like any journalist who’s been working for three decades, I’ve written and edited thousands of headlines on thousands of stories,” he says. “There is no way I would ever sign off on that headline and lead for that story. Our MediaBugs error-report filing called them ‘completely unsupported,’ and I agree.”
Go read Scott’s post for the stark details as to why — they are illuminating. When you run a story that you don’t have, as he puts it, and then defend it with misdirection and a high-handed tone, you only hurt your credibility more.
[In other MediaBugs news today, CJR's Craig Silverman talks with me about our new report on corrections practices across major U.S. news sites. Whereby I offer a crucial update to Fox News' "Fair and Balanced" slogan.]
Just about every professional journalist under the sun will tell you that accuracy and transparency in news reporting are essential to a media organization’s credibility. It would seem to follow, then, that most newsrooms would make tracking and correcting errors a priority — particularly in the digital age, in which they have unprecedented capability to interact with the public. But that’s not at all the case right now. Over at MediaBugs, Scott Rosenberg and I have just published our first major report on the state of corrections practices across the Bay Area news media. What we found will not boost public confidence:
The results of MediaBugs’ first survey of Bay Area media correction practices show that 21 out of 28 news sites examined — including many of the region’s leading daily newspapers and broadcast news outlets — provide no corrections link on their websites’ home pages and article pages. The websites for 17 of the 28 news organizations examined have no corrections policy or substantive corrections content at all.
Sites that do offer corrections-related content frequently make it relatively difficult to find: It is located two or three obscure clicks into the site, or requires visitors to use the site’s search function. Once located, the corrections content is, in most cases, poorly organized and not easily navigated.
In the above report, you can see the specific rundown for most major news outlets headquartered in or regularly covering the Bay Area (including some major national outlets). We’re not just looking to highlight these problems; we also hope to encourage news organizations to fix them — and the good news here is that the necessary improvements are pretty easy to make. To that end, we’ve also published a companion piece outlining best practices in error reporting and corrections.
Also see Scott’s excellent post over at MediaShift Idea Lab for more insight into why news sites have stopped short in this realm — and where we think they should be headed, most ambitiously. (Nutshell: Adding a “Report an error” button as a standard feature on every news page online. The promotion of which is a project in our pipeline.)