The Internet Archive hopes to boost its collections through funding from the Knight News Challenge
ABOUT                    SUBSCRIBE
June 23, 2009, 10:34 a.m.

MediaBugs rethinks corrections by taking a page from programmers

On their weekly podcast last month, NYU journalism professor Jay Rosen and programmer Dave Winer blended their backgrounds to propose a new way of conceiving errors in the news media. Corrections, they argued, should be treated like software bugs — a valued element of programming, recorded systematically in bug-tracking databases. “If you help us catch a bug — if you point it out — that’s good, because it helps us make the program better,” Rosen explained.

Not a revolutionary idea, but a good one, and when Tim Windsor pointed to it here, the suggestion of a bug-tracking system for news prompted an excellent question from Daniel Bachhuber: “So…who’s going to build it?”

Now we know. Scott Rosenberg, best known as the co-founder of Salon, has been mulling this idea for a while, and last week, he received a $335,000 grant from the Knight Foundation to build MediaBugs, the first correction-tracking system for news outlets in the San Francisco Bay Area.

Well, maybe not the first. One might argue that blogs already do a fine job at pointing out bugs in media. (That criticism of the project came up among the Knight News Challenge judges.) Many newspapers, meanwhile, already have thorough, internal systems for dealing with corrections submitted by readers. (On the other hand, some of those systems are broken.) And what if readers don’t want to visit a third-party site to deal with media mistakes, or if news organizations simply choose to ignore MediaBugs entirely? I posed those and other questions to Rosenberg at MIT last week, and you can see his responses in the video above.

Rosenberg’s site will be independent of media outlets in the Bay Area, but what if it worked like the mock-up I’ve created at right, as integral to news sites as the “email-this” button? One of the greatest impediments to an effective corrections process is that readers don’t know how to submit one. (I had an awful experience on Sunday night trying to find the Washington Post’s corrections page.) A bug-tracking system for news is a great idea, but it needs to be as easy as possible for readers and news organizations alike.

A full transcript of the video is after the jump.

Scott Rosenberg: It’s called MediaBugs.org. And the idea is to create a web site, a web service, that people in a community, in this case the San Francisco Bay Area, can bring problems and errors that they find in media coverage and post them and try to get them fixed. […]

The inspiration of the project is from what’s called a bug tracker in an open-source project. So if you’re developing open-source software, you have this project, and you put up a public website that anyone can bring these — file these bugs. If you’re using Firefox and something breaks, you go to their web site, and you tell them about it.

And that’s sort of, you know, both the practical inspiration but also a little bit of the philosophical inspiration because, really, one of my goals it to see if we can begin to alter the mentality or the mindset of journalists a little bit away from perceiving the person who comes and tells you about an error as a gadfly or a pest, which sometimes we do. I know I have. It’s a common and understandable reaction for newsrooms, for journalists to want to kind of circle the wagons when under attack or when perceived to be under attack. And I’m hoping that we can just turn that around a little bit and show people that, you know, actually, the person who’s reporting a problem or reporting an error, filing a bug, is someone who’s helping you because you want to know about that stuff and you want to fix it. […]

Well, certainly, the blogosphere does accomplish some of this. What doesn’t get accomplished — a couple things. One is it’s very scattered, right? You don’t have any sense of continuity. You can’t kind of aggregate the — you know, you just don’t see these things in context. But also, there is no record of the resolution. You don’t have, the concept — in a bug tracker, you have the concept of an open bug and a closed bug. An open bug is one that you’re still working or that has never been resolved. A closed one, you don’t have to think about anymore.

And I think it’s going to be really valuable to be able to do that with this kind of information and to gather data over time about, you know, which news organizations had more of these kinds of bugs filed. And it might be that, you know — which ones are resolving them. And at the end of it all, I’m hoping that we don’t — we’re not in a situation where somebody thinks, “oh, this paper had all these bugs filed. They must be doing a bad job.” But rather, “oh, this paper had all these bugs filed, and most or all of them were resolved. And that’s great. That is a good thing.” […]

Zach Seward: There are obviously several types of bugs that journalists might not consider a bug. Certainly questions of bias and opinion.

Rosenberg: Sure.

Seward: One, in particular, might be a bug of interpretation.

Rosenberg: Yeah.

Seward: I think we might all agree that several national newspapers had a bug in their coverage of WMD leading up to the Iraq War, right?

Rosenberg: One gigantic bug with many manifestations.

Seward: I can’t imagine that someone would — is it equipped to deal with that sort of bug, or is it more, you know, individual facts?

Rosenberg: The base focus is going to start with facts. Now, there’s not — you can’t easily divide all kinds of errors and problems into one pile of facts and one pile of opinions or interpretation. It’s a spectrum. And so, inevitably, this will bleed toward — into the center of that spectrum, and that’s fine.

I don’t think — this is not going to be the place on the web to go and argue that The New York Times is a left-wing rag or Fox News is not fair and — you know, there are so many places you can do that on the web already. That’s a fine thing, but we don’t need another place to have that argument.

So, you know, something like WMD, if MediaBugs had been around when, you know, some of those stories came out, I would hope that it would be a great place to file those bugs. It’s not going to be a single report that says, “The media are screwed up on WMD.” It’s going to be, “Judy Miller‘s story today was erroneous because a, b, and c. What will the newspaper do about that?” […]

So many of the exchanges today between people inside newsrooms and people on the web are overheated, right? There’s a lot of anger at the media, and now, today, there’s a lot of anger in the media at people on the web. And I think no single project is going to be able to change that, but I’m hopeful that we can begin to create a more civil exchange. And having this be a neutral ground is important to that.

A lot of people don’t trust their local media for one reason or another. Sometimes they’re not justified in that; sometimes they are. But they don’t even bother to go to the media outlet with their complaints. And then, a lot of — there are more and more journalists who have a kind of bunker mentality. They just don’t respond on the web because they were flamed once. And that’s understandable, but it’s a shame, I think. So, if we can begin to change that atmosphere, I’ll be very happy.

POSTED     June 23, 2009, 10:34 a.m.
PART OF A SERIES     Knight News Challenge 2009
Show comments  
Show tags
Join the 15,000 who get the freshest future-of-journalism news in our daily email.
The Internet Archive hopes to boost its collections through funding from the Knight News Challenge
The home of the Wayback Machine and other efforts to preserve the Internet is among 22 projects based around libraries receiving $3 million in funding through the Knight News Challenge.
Constantly tweaking: How The Guardian continues to develop its in-house analytics system
Since its launch in 2011, The Guardian has consistently made changes to its in-house analytics tool, Ophan.
Bloomberg Business’ new look has made a splash — but don’t just call it a redesign
Bloomberg digital editor Joshua Topolsky on uncomfortable news design, new ad units, and why they killed the comments.
What to read next
Don’t try too hard to please Twitter — and other lessons from The New York Times’ social media desk
The team that runs the Times’ Twitter accounts looked back on what they learned — what worked, what didn’t — from running @NYTimes in 2014.
728From explainers to sounds that make you go “Whoa!”: The 4 types of audio that people share
How can public radio make audio that breaks big on social media? A NPR experiment identified what makes a piece of audio go viral.
722Q&A: Amy O’Leary on eight years of navigating digital culture change at The New York Times
“In 2007, as digital people, we were expected to be 100 percent deferent to all traditional processes. We weren’t to bother reporters or encourage them to operate differently at all, because what they were doing was the very core of our journalism.”
These stories are our most popular on Twitter over the past 30 days.
See all our most recent pieces ➚
Encyclo is our encyclopedia of the future of news, chronicling the key players in journalism’s evolution.
Here are a few of the entries you’ll find in Encyclo.   Get the full Encyclo ➚
Investigative Reporting Workshop
News Corp
Vox Media
Windy Citizen
Current TV