Apple's stock took a tumble when popular tech blog Engadget posted a supposed "internal memo" indicating a significant delay in the releases of the much-anticipated iPhone handheld device and the Leopard operating system. The memo was a fake; Engadget had been fooled.
The blog later called the original post a "false alarm," and Apple's stock rebounded--though not to its preplunge levels. As TechCrunch blogger Michael Arrington said in a post Thursday evening, "Many investors had lost a staggering amount of money in the amount of time it takes to brush your teeth."
For millions of online news junkies, gadget enthusiasts, and Apple stockholders, "Applegate" has become a reminder of a very old lesson: Don't believe everything you read.
The publication of erroneous rumors, incorrect facts--Dewey didn't actually defeat Truman, as we all know--and pranks that were taken too seriously (, anyone?) has plagued the media industry since its earliest days. It's no secret, however, that the Internet and blogging have changed the landscape entirely.
With push-button publishing, publications no longer have a day's wait to break news--a two-minute call to confirm a scoop can mean that another site breaks the news first. With the availability of so much information, and the ability to immediately connect with so many people and then broadcast a message, the online world has also proven to be a formidable engine for rumors. Some are true. Some aren't. Either way, the Web audience's appetite for gossip seems inexhaustible.
"I've always been one to post rumors," said Brian Lam, editor of Gizmodo, a rival blog to Engadget. "Even the really gnarly rumors. I love them."
Add to that a company like Apple--notoriously secretive and holding a loyal band of followers eager to snap up any leaked details, from patent filings to fuzzy camera phone pictures of what may or may not be the next iteration of the iPod. "The important thing on the juicy stories is to be extremely cautious," Lam said, "especially (with) Apple, because those guys are crazy. The fanboys are crazy."
That's a lesson Lam learned in December when he wrote a post promising
In retrospect, Lam said, things would've been done a little differently. "I wouldn't have tagged (the post with) 'Apple' in the first place, and I wouldn't have apologized," he said. "I really think I left myself open when I apologized, because I think if it was set up as a prank, it should have just been taken as a prank. It was totally scary."
Since then, he said, he's become more aware of the impact that a blog post can have. "You can just play it fast and loose," Lam said in reference to bloggers who might snap up the slightest and least-substantiated of rumors. "But I turn my game face on for anything with Apple or Microsoft. I don't f*** around, because it's too important."
It could be debated endlessly whether Engadget blogger Ryan Block, who posted the fake memo, should have acted differently. After all, he likely had to choose between looking into the veracity of the memo or quickly publishing the post before another tech blog beat Engadget to the punch. "I think it was a bit of a knee-jerk reaction to get out first, and I understand that, and I respect that," Gizmodo's Lam said. "There isn't enough time to do everything. That's why Ryan's not at fault."
Engadget's readers, at least the ones who commented on Block's apology post Thursday, seem to be on the same wavelength. "Seriously, I can always forgive the media," said one of them. "I don't see anything wrong with what you did, Ryan--any journalist would have done the exact same thing," another said. Yes, a few were miffed (including some who claimed to own Apple stock) but the overall mood of the commenters was forgiving.
Would readers cut The New York Times the same slack? Blog readers are a young, tech-savvy set who appreciate the speed at which bloggers like those at Engadget churn out the news. Newspaper readers might not demand the same kind of reporting speed, and they value a publications' attention to detail. So it's tough to say whether such an error like Engadget's would've gone over at a major newspaper without any pink slips in the aftermath.