greeleytribune.com
The Greeley Tribune offered some of the best MSM coverage of today's Windsor, CO tornado. But I first heard the news on Twitter. |
Earlier this afternoon, while I was working at my home office in Boulder, Colo., fellow blogger
Karoli (who lives in Calif.)
sent me a message on Twitter: "@agahran you out there? What's going on in CO?"
A little baffled, I responded: "@Karoli What's going on in CO in what respect? Fast-changing weather, other than that I'm just working. Seeing Indy Jones movie tonight."
She then posted something that got my full attention: "@agahran I'm seeing reports here on twitter of one killed near touchdown of tornado in Ft. Collins." And seconds later: "@agahran one killed, school badly damaged."
Ft. Collins is just about an hour north of Boulder. I have close friends who live there, and they have a child in elementary school. I figured, though, that they had more important things to do at the moment than take a phone call from me. I sent a text message to my friend asking if all was well, and continued my information scan.
I went straight to the National Weather Service site -- which is, I must say, a usability nightmare for someone seeking information about local severe weather in a hurry! I tried posting to Twitter links to specific NWS storm warnings, but apparently those pages are generated with session-specific URLs and so are useless if you send them as links to other Web users. (For future reference, it's probably best to post links to NWS pages for state-specific current watches, warnings, and advisories -- like this one for Colorado, so they can find the most up-to-date info for their part of the state.)
Next I jumped to the Ft. Collins Coloradoan site, where I found this report on the storm. That's where I learned that the tornado actually touched down in Windsor, a town several miles southeast of Fort Collins (and much closer to the town of Greeley). Karoli sent me a links to video and photos of the large tornado, shot by a 9News team. I watched the video while looking out my window and noticing the sky above was growing darker. (UPDATE: Here's more 9news video from during and after the tornado )
I tried tuning in online to Colorado Public Radio News, and then to Boulder community radio KGNU, but both offered only regular programming. I tried the local 9News site, but their video player didn't work in the first two Web browsers I tried. (Yes, I could have gone downstairs to turn on the TV, but I was already getting so much info online that I didn't feel compelled to do that. I felt I could monitor the situation better from my computer.)
tweetscan.com
Here's what Twitter users were posting about the Windsor, Colo. tornado today. |
So I jumped back to Twitter for more leads -- specifically
TweetScan, a good tool for searching Twitter for current posts that use specific keywords, like
tornado. This yielded several useful points of reference, such as a link to the
Greeley Tribune's blog-like, quick-updates-style coverage. Also on Tweetscan I saw mentions that the tornado-bearing storm was now heading toward Loveland, Colo. (closer to Boulder), with a link to the
Loveland Reporter-Herald's warning.
I then remembered that someone had set up a Twitter account, COtweeters, that Twitter users in Colo. use to share local information -- usually about informal get-togethers, but occasionally for other things. I suspected that, like me, some other locals might have Twitter running on their computers (or alerts coming to their cell phones) but not be paying attention to mainstream media at the moment.
So to give locals a heads-up, I posted: "@COtweeters: Tornado hit Windsor. Whole Front Range under tornado watch today." I followed up by posting links to the reporting by some local news sites, as well as the text of some NWS updates, ending with: "THE STORM THAT PROMPTED THE WARNING HAS HAS MOVED INTO LARIMER COUNTY AND NO LONGER APPEARS TO BE PRODUCING A TORNADO."
...The point of this tale is to show how Twitter's popularity has reached the point that it can be a valuable early warning system to nearly anyone -- including journalists and news orgs.
So, if you haven't done so already:
- Set up some Twitter accounts: This takes just a few seconds. You'll need one "official" one for your news org (like KPBS News did), and then make sure reporters have individual accounts.
- Learn to use Twitter when it's not an emergency. Twitter is extremely easy to use and fast to learn -- but it does take a little time to get comfortable with.
- Find local Twitter users by searching TwitterLocal for a radius around a state, city, or zip code. Subscribe to the RSS feed for the result of that search in your feed reader you can check it periodically for an overview of local discussions. Use TwitterLocal to identify some local users you can follow on Twitter regularly. With experimentation and experience, you'll figure out which local users tend to offer the best tips and insight. And of course, whenever news breaks anywhere, Twitterlocal can help you find what people from the affected area are posting.
- Learn to use TweetScan to check up on breaking news or events. There are some tricks -- like today, searching for "tornado" was far more useful than "Colorado," "CO," or "Fort Collins." Again, it's better to figure that stuff out when you're not covering a breaking story.
Of course, Twitter cannot and should not replace traditional reporting techniques, like calling sources and getting photographers on the scene. But this service has become extremely popular, which makes it a powerful resource for timely, diverse information. On May 15, Web analytics firm Compete.com reported that each month Twitter attracts 1.2 million users worldwide, a quarter of whom are "heavy users." So whenever your newsroom is chasing a breaking story anywhere in the world, it's probably a good idea to have someone watching Twitter and passing along useful leads from it to your reporters.
...The Boulder skies are clear again, now. And my Ft. Collins friend just texted me back to say all is well with his family.