Michael Moore Lashes Out At BuzzFeed, And Few Jump To Its Defense
By Christopher Zara | February 27, 2013 7:51 AM EST
BuzzFeed is once again being lambasted for its reporting -- this time by the filmmaker Michael Moore -- and much like the last time this happened, the viral-news website is finding few defenders from within the journalism community.
Moore went on a Twitter tirade on Tuesday afternoon after an article by Tessa Stuart, a Los Angeles-based BuzzFeed reporter, implied that he exaggerated some of the facts regarding a story about a Palestinian filmmaker being detained at Los Angeles International Airport. Moore had been tweeting about his efforts to vouch for Emad Burnat, the Oscar-nominated co-director of “5 Broken Cameras,” who said he and his family were detained for some 90 minutes at U.S. Customs and Border Protection when they arrived at LAX from Turkey.
According to Moore and Burnat’s version of the story, customs officers threatened Burnat with deportation if he could not produce documents proving that he was invited to Sunday’s Academy Awards ceremony. Burnat -- who is Palestinian, and whose wife was wearing a hijab -- showed the officers the invitation that was sent to all Oscar nominees, but that allegedly wasn’t good enough. According to Moore’s tweets, it was only after Moore personally vouched for Burnat that the filmmaker was permitted into the country.
However, BuzzFeed’s article, first posted on Monday, called that version of the story into question. In it, Stuart cited an LAX source “familiar with the situation” who said that Burnat was held only for 25 minutes and released after he produced his Oscar ticket. The source claimed that Moore and Burnat were overplaying the incident for publicity.
When Moore caught wind of the BuzzFeed piece, his Twitter tirade began with an ultimatum directed at Stuart, which Moore tweeted at 7:15 on Monday evening:
Tessa Stuart of Buzzfeed has lied about the Palestinian filmmaker detained at LAX and I can prove it. Tessa, I'll give u an hr to correct.— Michael Moore (@MMFlint) February 26, 2013
Fifteen minutes later, the following tweet appeared:
Feel bad for you, being snookered by Homeland Security. Re-read your story and look for the clue of how u got used. #journalismisdead— Michael Moore (@MMFlint) February 26, 2013
And finally, this:
Time's up. Buzzfeed today tried to raise doubts that Oscar nominee, Palestinian filmmaker Emad Burnat wasn't really detained at LAX on Tues.— Michael Moore (@MMFlint) February 26, 2013
Continuing in a series of tweets, Moore proceeded to call Stuart’s source’s version of the story an “outright lie.” The “Fahrenheit 9/11” filmmaker went on to explain that Burnat could not have shown an Oscar ticket to customs officers -- as Stuart’s source claims -- because physical tickets weren’t issued to any of the Oscar attendees until the Thursday before the ceremony.
“It’s that way every year,” Moore continued. “Oscar tickets are available only on Thursday through Saturday, the day before the Oscars.”
Stuart later updated her story with Moore’s tweeted version of what happened. (She had also apparently been trying via Twitter to get him to tell her his side of the story directly.) In her update, she explained that the differences in the two stories hinge upon what type of documentation Burnat was asked to produce to customs officers. Was it a ticket, an invitation or something else? She wrote that she had reached out to her source at LAX for clarification but had not yet heard back.
As of early Tuesday afternoon, Stuart’s story had still not been updated. In an email to IBTimes, Stuart said she is still reporting on the incident and that new information would be added shortly.
Meanwhile, media reporters have been running amok with the “BuzzFeed vs. Michael Moore” narrative, with many either taking Moore’s side or publishing stories that bolster his account. The Hollywood Reporter’s Jordan Zakarin quoted a representative for the filmmakers who backed up Moore’s claim. Blasting BuzzFeed, the rep told THR via email, “It’s pretty insensitive to attempt to minimize anguish of this experience for Emad and his family.”
The Atlantic Wire’s Alex Abad-Santos wrote in a blog post Tuesday morning that “Someone’s not telling the truth about what happened,” adding that, at least for now, BuzzFeed appears “to be on the losing end of this one.” Abad-Santos noted that the original subhead and first sentence of Stuart’s article referred to “sources” at LAX that have refuted Moore’s account. As it turns out, Stuart talked to only a single source, a fact that was later clarified in a correction posted at the end of Stuart’s article.
Stuart, a former reporter for LA Weekly, joined BuzzFeed in December, according to FishbowlLA -- just two months after BuzzFeed announced it was opening a Los Angeles bureau. In January, the rapidly growing website announced that it had raised another $19.3 million in Series D financing led by the venture capital firm New Enterprise Associates.
But that growth has not come without its growing pains, as this latest debacle shows, and this is not the first time BuzzFeed has been called out in recent months for its reporting. In December, the website found itself in hot water after contributor Jack Stuef published a would-be expose on The Oatmeal cartoonist Matthew Inman in which Stuef characterized Inman as a Republican and, essentially, a hypocrite. However, Inman posted a lengthy rebuttal to the piece, revealing that Stuef had built his thesis partially around an online profile that, it turned out, didn’t belong to Inman. BuzzFeed’s editor, Ben Stein, later told GigaOM that he regretted the “major factual error.” Then, like this week, no shortage of media reporters jumped on the story, eager to report on BuzzFeed’s mistake.
Moore, for his part, said via Twitter that he was not looking to shame the website. “Sorry you guys had to go through this,” he tweeted just after midnight Tuesday morning. “I did not want to publicly embarrass you. I like Buzzfeed.”
To contact the editor, e-mail:
Most Popular Slideshows
- NFL MNF: Pittsburgh Steelers 30, Houston Texans 23 [PHOTOS]
- 2014 MLB World Series Game 1: San Francisco Giants 7, Kansas City Royals 1 [PHOTOS]
- 2014 MLB World Series - Game 2: Kansas City Royals 7, San Francisco Giants 2 [PHOTOS]
- NFL Thursday Recap - Denver Broncos 35, San Diego Chargers 21: Peyton Manning Has 3 TDs In Easy Win [PHOTOS]
Join the Conversation
- The Burka Avenger Educates Children While Fighting For Girls' Education Rights In New Pakistan TV Show
- Christopher Walken To Play Mob Boss In Film Adaptation Of Four Seasons Musical 'Jersey Boys'
- William Cantrell Mistakes Human Ashes For Cocaine, May Have Snorted Remains
- Giant Alligator Eats 80-Pound Dog In North Carolina, Gator May Still Be Alive
- Steve McQueen's Last Ride, 1952 Custom Chevy Pickup Truck, Hits The Auction Block
- Xiaomi Redmi 1S vs. Sharp Aquos Crystal – Specifications, Features And Price Showdown
- ASUS Releases A Teaser Indicating The Arrival of New Zenfone and ZenWatch On October 28
- Boy Stoned To Death For Alleged Rape, Victim Receives Dowry From Militants
- Three Dual SIM Samsung Galaxy Note 4 Duos Variants Comes To China
- Update HTC One M7 with LG G2 with Android 4.4.2 as Sprint OTA: Fixes and Installation
- Russia is Creating Underwater Combat Robots to Protect its Arctic Territories
- Verizon Motorola Droid Turbo Leaked Live Images Surfaces, Scheduled To Get Unveiled On Oct 28