Editor’s note (April 2025): This article is part of Blog Herald’s editorial archive. Originally published in 2008, it has been reviewed and updated to ensure accuracy and relevance for today’s readers.
In December 2008, a Continental Airlines flight skidded off the runway at Denver International Airport. The plane caught fire. Passengers scrambled to escape. And while emergency crews were still responding, a man named Mike Wilson — Twitter handle @2drinksbehind — was already publishing eyewitness updates from the scene.
His tweets weren’t polished. They weren’t verified by an editor. But they were immediate, specific, and human in a way no newscast could match. The Blog Herald covered the moment at the time, noting how Silicon Alley Insider scrambled to screenshot the timeline before it could disappear. What felt like a novelty in 2008 turned out to be a preview of something much larger — a fundamental shift in how breaking news reaches people, and who gets to tell it.
The moment that changed the script
Before the Denver crash, Twitter was still largely dismissed as a platform for broadcasting what you had for lunch. The idea that it could serve as a real-time wire service — one operated by ordinary people caught inside the news itself — hadn’t really landed yet.
Wilson’s tweets changed that. He wasn’t a journalist. He was a passenger who happened to have a mobile phone and an account. He described the impact, the smoke, the evacuation. He noted, crucially, that people were walking away. That detail — no fatalities — reached his followers before any official statement was issued.
Silicon Alley Insider recognized what it was seeing and screenshotted the thread. Within hours, the story wasn’t just the crash. It was the Twitter feed about the crash. Mainstream outlets picked it up. Journalism professors started citing it. The phrase “citizen journalism” got a lot more serious.
Fortunately, no one was killed in the accident. That fact matters — both because it’s the right outcome and because it meant this story could be celebrated rather than complicated by grief.
What it actually meant for bloggers and creators
The Denver crash moment landed in the middle of a broader conversation about what blogging and digital publishing could be. At the time, Mashable was publishing exhaustive lists of mobile tools for exactly this kind of reporting. The infrastructure for citizen journalism was being assembled in real time.
For bloggers specifically, the lesson was direct: proximity is a form of authority. You don’t have to be credentialed to be credible. If you’re there, and you can write clearly and honestly about what you’re seeing, people will read it — and sometimes your account will outlast the official one.
That principle has only deepened since. The tools have changed dramatically. In 2008, you were working with a basic mobile browser and a character limit. Today, a blogger or creator on the ground has access to live video, Stories, Threads, real-time collaborative documents. The barrier to publishing breaking eyewitness content is essentially zero.
What hasn’t changed is the underlying dynamic: audiences trust proximity. A shaky iPhone video from inside an event will almost always command more attention than a polished studio report filed hours later.
The complications that followed
But the Denver crash was also, in retrospect, a best-case scenario. The tweets were accurate. No one died. The story was contained. What emerged over the following years was more complicated.
As Twitter became the default channel for breaking news, the problems scaled alongside the opportunity. The 2013 Boston Marathon bombing coverage became a case study in how badly crowdsourced identification can go — with Reddit communities and Twitter users wrongly naming innocent people as suspects, causing real harm to real families. The platform’s speed, which had looked like a pure asset in 2008, turned out to carry serious liability.
For bloggers and content creators, this created a tension that still hasn’t fully resolved. The expectation from audiences is immediacy. The responsibility of publishing — even informally, even from a personal account — requires care. Speed and accuracy have always been in tension in journalism. Social media made that tension visible to everyone, not just professionals.
The instinct to tweet first and verify later isn’t just a media ethics problem. It’s a creator problem. Bloggers who built audiences on being first to cover breaking stories discovered that one bad call — one amplified rumor, one screenshot taken out of context — could undermine years of trust.
Platform dependency and the fragility of the feed
There’s another layer worth examining here. The original story depended on Twitter. The screenshots, the archiving, the spread — all of it ran through a single platform. In 2008, that felt like a feature. In 2025, it reads as a warning.
Twitter no longer operates the way it did. The platform has been renamed, restructured, and algorithmically reshuffled multiple times since the Denver crash. Accounts get suspended, threads disappear, and the discoverability of older content has degraded significantly. If @2drinksbehind’s original thread still exists in some form, finding it organically is nearly impossible.
This is the quiet lesson beneath the more celebrated one. The Denver crash story demonstrated the power of real-time public publishing. But it also showed how dependent that power is on the infrastructure of a single company — infrastructure that can change without notice and without your consent.
Bloggers who own their platforms have always had a structural advantage here. A post on your own domain doesn’t disappear when a social network pivots its algorithm or changes ownership. The engagement may be slower to build, but the archive belongs to you.
What the moment still teaches us
The @2drinksbehind story gets cited less often now. It’s been overtaken by dozens of more dramatic examples — events that were larger, more consequential, more contested. But the core insight it offered remains useful.
Audiences want to hear from people who were there. Not because those people are necessarily right, but because their proximity is real. The challenge for creators and bloggers is to earn that trust honestly — by being accurate, by acknowledging what you don’t know, and by treating your audience as people who deserve the truth rather than the fastest take.
The tools have changed. The speed has increased. The stakes, if anything, are higher. But the question @2drinksbehind answered in 2008 is still the one worth asking: when something happens and you’re there to see it, what do you owe the people who weren’t?
