If you’ve been visiting MediaBugs.org this week you may have noticed that the site is intermittently very slow to load. We’re so sorry for this.

It’s not the fault of our software, but rather, a problem with our ISP, MediaTemple. Several thousand of their customers seem to have been affected. And they’re working on it.

With any luck it will all be over soon. In the meantime, our apologies.

UPDATE 5/14/2010: After intermittent ISP troubles throughout the past two weeks we seem to be out of the woods. As of a couple of days ago MediaTemple reported that they’ve dealt with the problem, and we’ve noticed no slowness on the site — but if you do by all means let us know!

 Report an error

MediaBugs was originally proposed as an experiment in correcting errors in news coverage. But what, exactly, is an error?

We’ve concentrated our efforts on the notion of “correctable errors,” which means, primarily, errors of fact, or sometimes of context and emphasis.

A handful of our early bug reports have been more in the area of bad grammar, questionable sentence structure, cliched phrasing and so forth — the realm, traditionally, of copy-editing, an art and vocation that is, sadly but probably irreversibly, in decline.

Personally I would rather see MediaBugs reports concentrated more in the realm of errors than of copyediting. (For a different sort of experiment in collaborative online copyediting,but one that’s very much in the MediaBugs spirit, check out Goosegrade/Editz.) But we’re committed to being guided to some extent by our users as long as what they’re doing is roughly aligned with our project goals.

What do you think — should MediaBugs take on all sorts of small copyedits? Should it delete them and focus on the factual/substantive stuff? Or maybe accept the copyedits but somehow segregate them on the site?

 Report an error

Today we’re removing the drapes and unveiling MediaBugs to the world. We’re still in beta mode, which means that we’ll probably be fixing our own bugs and spiffing up the place for some time. But everything’s in place for you to use MediaBugs to help fix the news, beginning now.

You can register, learn more about our bug criteria, and check out recent bugs. And by all means send us comments and questions and tell us about any problems you encounter!

 Report an error

Welcome to the “closed beta” of MediaBugs.

Um, what’s a closed beta, you ask? Truth is, it’s not really all that closed. We’re giving accounts to pretty much anyone who asks. We haven’t locked our test site away behind a lock and key. We’re just not heavily promoting it or passing around its URL while we get things in order.

What we are doing is inviting a relatively small group of people — friends, well-wishers, experts, people who’ve told us they’re interested in the project — to help us in two ways before we fling open the doors more widely:

(1) Reporting some errors in news coverage, some initial media bugs that we can seed the site with — so that those people who come by once we’re more fully public can get a quick sense of what we’re all about and how things work here.

(2) Reporting our bugs back to us so that we can provide the wider public with as smooth an experience as possible.

We’re figuring on this phase lasting two to four weeks. If you want to help out, just get in touch and we’ll send you the seekrit entry info.

 Report an error

After long but happy labors in the trenches we’re close to having a site and service ready for people to use!

Over the next few days we’ll be doing a final cleanup and then inviting in a small bunch of initial users to kick the tires, find our own bugs, and give us a first round of feedback.

Some of you have already asked to help out — thanks! If you’re interested in joining in, let us know — just email us at info [at] mediabugs.org.

And for those of you who’ll be at SXSW, I’ll be there too — pull me aside and I’ll give you a demo.

 Report an error

MediaBugs is filling out its roster.

I’m super pleased to announce that Mark Follman is joining the project as associate director and community manager. Mark, who I had the pleasure of working with for many years at Salon, has strong experience both in the journalism trenches and also in the relatively novel field of online conversation management.

I was delighted, and humbled, by both the number and the quality of applicants for this post. I know there are a lot of journalists looking for gigs today, but MediaBugs is a pretty unconventional opportunity. Thanks to everyone who threw a hat into the ring. I hope you’ll all continue to keep up with what we’re working on here, and I apologize that I couldn’t interview every single one of you!

We’ve also chosen our technical design and development partner. Until recently the name Ben Brown was familiar to me chiefly because I’d long ago read entertainingly caustic rants by him (and reread them during my research for Say Everything). I knew that Brown had a long and storied career on the Web; but I didn’t realize, until our adviser Lane Becker pointed me in his direction, that he’s also an ace developer. His company XOXCO has done some great projects, most recently NeighborGoods, and we’re very excited to be working with him to transform MediaBugs from an idea into a smoothly working, intuitive site.

More soon as we pick up speed…

 Report an error

Americans trust the news media less than ever: “Just 29% of Americans say that news organizations generally get the facts straight, while 63% say that news stories are often inaccurate,” according to the latest results from the Pew Research Center released this week. That represents a drop of 10 percentage points from 2007, when 53% of Americans said that news stories were often inaccurate. And an alarming 70 percent of people surveyed believe that news organizations “try to cover up their mistakes.”

There’s a problem here, for sure. Many journalists understand this and work hard, every day, to try to solve it. Others are in denial. In reaction to this report, journalism scholar Jay Rosen wrote the following series of tweets yesterday:

Top explanations from journalists for fall in public confidence: 1. All institutions less trusted; 2. Cable shout-fest; 3. Attacks take toll

Top explanations from journalists for fall in public confidence, cont. 4. Environment more partisan; 5. Public confusion: news vs. opinion.

Top explanations from journalists for fall in public confidence, cont. 6. People want an echo chamber; 7. Numbers don’t really show a fall.

Each of these explanations doubtless has some merit. But together they constitute a kind of head-in-the-sand stance. Missing from the list is the simplest, most obvious explanation of all: Maybe we’ve lost confidence in the press because of its record of making mistakes and failing to correct most of them.

In other words, perhaps so many people think the news is full of inaccuracies because, er, they’re right.

Read Craig Silverman’s excellent book Regret the Error, based on his blog of the same name, and you’ll learn the sad numbers from the best studies we have on this topic: They show that the percentage of stories that contain errors ranges from 41 to 60 percent. Scott Maier, a journalism professor at the University of Oregon who has studied this field, tells Silverman that he found errors are “far more persistent than journalists would think and very close to what the public insists, which I had doubted.” Only a “minuscule” number of these errors are ever corrected.

Some of these errors are substantive, others seemingly trivial. But each one of them leaves readers or sources who know the topic shaking their heads, wondering how much else of the publication’s work to trust.

Since reversing this dynamic is the central goal of MediaBugs, we’ll be writing about it a lot here.

 Report an error

In a recent Washington Post column, the eminent editor and essayist Michael Kinsley argued that newspapers overdo it when it comes to correcting small errors. Kinsley mocks the New York Times for its attention to correcting such trivia as the name of a company called Voxox (it had been printed as “Vovox”) or that of the College of William & Mary (misprinted as William and Mary College):

Although the purpose of [the daily Corrections column] is to demonstrate the Times’s rectitude about taking facts seriously, the facts it corrects are generally so bizarre or trivial and its tone so schoolmarmish that the effect is to make the whole pursuit of factual accuracy seem ridiculous.

“Bizarre or trivial”? Really? I think these goofs look rather different to the folks at Voxox or the College of William & Mary. And the importance of correcting them lies not in some earth-shattering import to the facts themselves but rather in the bond of trust that is established when a publication is seen to care enough to correct them — and, inversely, the loss of trust that occurs when the publication doesn’t bother.

Remember that, for Joe at Voxox or Sue at William & Mary, the misspelled name isn’t just a tiny fact in a sea of information; it represents that person’s point of maximum contact with the publication. Each time these people think of that newspaper or magazine they’re going to remember, These are the folks who couldn’t even get my name right. Multiply that by all the careless errors that get made in the course of normal journalism and you can get some insight into why public trust in the media has been on a downhill curve for so many years.

On the Web, of course, when these errors happen, we get to talk back, and share our discontent, and begin to see that it is not uncommon.

Kinsley maintains that most gripes with the news are driven by partisanship:

The fad for elaborate and abject corrections, and factual accuracy in general, is based on the misperception that when people complain about the media getting it all wrong, what bothers them is that the newspaper identified the mountain inside Denali National Park as Mount Denali (as it is “referred to by many,” the Times defensively put it the other day) and not by its official name of Mount McKinley, which “has not been officially changed.” Nor do they care whether a reporter “misstated the size of the National Hockey League when Ed Johnston — a retired goaltender who is a proponent of safer headgear — helped the Boston Bruins win Stanley Cup titles in 1970 and 1972.” What bothers people is the refusal of the Times and other papers to call President Obama a socialist or a Muslim, or to say outright that talk radio hosts are vermin. In short, most complainers tend to be ideologues whose vision of an accurate newspaper is far different from that of the professionals.

Certainly, the Web teems with angry people on both left and right who are unhappy with the media. Satisfying any of them is an uphill and perhaps futile effort. But there’s a much wider population that has lost faith in the media for the simpler reason that, in their experience, reporters simply get too much wrong. It is for those people that the managing editors of the world devote a portion of their time and energy to fixing the spellings of names and other minor goofs — and coming clean about those fixes.

If your newsroom doesn’t make a commitment to fixing such errors publicly, then people will stop bothering to report them to you. They’ll assume you don’t care, and they’ll be correct. This downward spiral has already begun in many communities.

Our hope in starting MediaBugs is to begin the painstaking work of reversing this dynamic. We don’t think that it will be fast or easy. It’s a lot more difficult to win trust than to lose it. But it’s worth the effort!

 Report an error

Welcome to the MediaBugs blog! This is where we’ll be offering updates on the MediaBugs project, a winner of the 2009 round of the Knight News Challenge.

MediaBugs will be a place on the Web where people can bring errors and problems they’ve found in media coverage in their community, and try to get them fixed. We aim to provide a neutral ground where journalists and the public can work together to improve news coverage. Our pilot project is in the San Francisco Bay Area. We’re starting work on it now and expect to have a test version of the site up this coming winter.

You can read our Frequently Asked Questions page here.

 Report an error