SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Politics : Politics for Pros- moderated

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
From: LindyBill5/22/2005 3:34:59 PM
   of 793917
 
Newsweek: We're Really Sorry Even Though We Did Nothing Wrong

By Captain Ed on Media Watch

Newsweek again issued a mea culpa for its false report of Qu'ran desecration, this time issued from Richard Smith, the magazine's editor-in-chief. As in previous statements from the magazine, the apology comes complete with an explanation of how they didn't do anything wrong and that the Pentagon bears responsibility for not stopping them from printing the story:

"As most of you know, we have unequivocally retracted our story. In the light of the Pentagon's denials and our source's changing position on the allegation, the only responsible course was to say that we no longer stand by our story.

We have also offered a sincere apology to our readers and especially to anyone affected by violence that may have been related to what we published. To the extent that our story played a role in contributing to such violence, we are deeply sorry. ...

One of the frustrating aspects of our initial inquiry is that we seem to have taken so many appropriate steps in reporting the Guantanamo story. On the basis of what we know now, I've seen nothing to suggest that our people acted unethically or unprofessionally. Veteran reporter Michael Isikoff relied on a well-placed and historically reliable government source. We sought comment from one military spokesman (he declined) and provided the entire story to a senior Defense Department official, who disputed one assertion (which we changed) and said nothing about the charge of abusing the Qur'an. Had he objected to the allegations, I am confident that we would have at the very least revised the item, but we mistakenly took the official's silence for confirmation."

As in Newsweek's earlier missives, they continue to apologive while claiming to lack understanding why the story went wrong. Never do they think to question the basic premise of what they were told. Did it make sense to anyone at Newsweek that interrogators would get better response from Islamists by desecrating their holy book? It didn't pass the smell test for me when I first heard it, and it still doesn't to this day. Newspaper reporters should have some sense of skepticism, especially in direct proportion to the sensationalism of the story, and Isikoff and his editors applied theirs in inverse proportion.

Another question is the newsworthiness of the story. Flushing Qu'rans breaks no Geneva Convention or treaty, and to describe it as "abuse" insults the readers' intelligence, even if true. Smith never addresses the editorial decision that concluded this story worthy of reporting, or on what basis that decision was made. Since Newsweek still has not reported the strict guidelines set down by the military for handling the Qu'ran, it hasn't even the excuse that they found someone violating a military rule. Clearly, Newsweek wanted to run with a sensational story despite a lack of any real newsworthiness, one that would generate a lot of publicity for the magazine. Who made that decision, and why? How will Newsweek stop that from happening again? Smith doesn't address that.

In short, while the pleas for mercy now originate at the top and use more effusive language, the message has remained the same -- we're sorry for doing nothing wrong, we won't explain our editorial decisions in running this story, and it's all the Pentagon's fault for not stopping us. Smith should have saved himself the trouble.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext