Mistaken identity in the Twitter age

I cannot remember the first time I was told not to take police scanner traffic as gospel, nor who told me, but in my career as a journalist that advice has served me quite well over the past 25 years.

Oh it's a great tool. The dispatchers on the other end can help you find out where the fire equipment is traveling. But that report cannot tell you if there really is a fire until there are eyes on the scene. Scanner traffic can let you know police and rescue are responding to the report of a crash. But it doesn't tell you anything about the crash. Use the scanner for tips, we were always told, but you need to confirm anything you report.

Tell that to the families of Sunil Tripathi, and if there really is such a person as Mike Mulugeta. Twitter lit up about midnight Pacific time last night with those two names, as a number of people tweeted that they had heard those names over police radios as the suspects in the shooting of an MIT police officer, and later the suspects in the Boston Marathon bombing. People ran with the names and they trended on Twitter. Some even said that Mulugeta had been shot dead and the police were going door-to-door in Watertown, Mass., looking for Tripathi.

When I woke up this morning, it turned out there had been a change in the story, and Tripathi and Mulugeta were no longer the suspects. Instead, two brothers of Chechnyan descent, Dzhokhar and Tamerlan Tsarnaev, were connected to all the crimes, with Tamerlan (Suspect 1) dying after being taken into custody.

I'll let the current events play themselves out without any comment, but the rapid spread of the wrong names is an issue I cannot ignore. I especially feel bad for the family of Tripathi, a Brown University student who has been missing for about a month. They had to take down the Facebook page they were using to generate tips on his possible whereabouts when it was overrun with people thinking he had committed these crimes.

As I have stated before, both in print and on this blog, Twitter and Facebook put some powerful tools in the hands of people who might not use them for the best purposes. I am sure most of the people who used the incorrect names did not do it with malicious intent, but ultimately the shoot first and apologize later nature of social media has caused issues that will never be rectified.

Meanwhile, it is yet another example of why I was always extra-careful with scanner traffic. I know I had a few reporters who got sick of me telling them we needed more information before we could run with something, especially after a television station moved into our market and started putting scanner traffic up on its website. To make matters worse, once our digital media manager got her hands on Twitter, she started doing the same thing, and I had to explain to reporters why she could do it, but I would not allow them to take that shortcut.

I hate to say I told you so on such an important issue, but, well, you know...

A test for social media

Getting ready for my Community Emergency Response Team class tonight and watching the coverage of Hurricane Sandy, and I had a few thoughts.

During the first week's class, our instructor, who really did help "write the book" that the feds now use for CERT training, stressed over and over that people need to get on Twitter -- they don't even have to tweet -- so they can keep tabs on things whenever there is an emergency. It's a thought I passed along to a few recalcitrant friends, although at least one who also refuses to join Facebook was a bit snarky in his response (which makes me think he'd have an even BETTER time doing the back-and-forth on Twitter).

Of course, social media is only as good as the people who are posting make it. And in the early hours of the storm, it has been a bit bumpy.

We've already had a bit of an online tussle about a photo at the Tomb of the Unknowns. Taken during a storm last month, some have retweeted or shared it stating that the three soldiers are out in hurricane conditions right now. While it is true soldiers are out there, the Old Guard quickly noted that what is circulating is not a current photo, and put some up at http://www.facebook.com/media/set/?set=a.515517068472407.121621.109701809053937&type=1  They are no less dramatic than the ones making the rounds, and have the added benefit of truly reflecting what's going on.

This actually is not what I'm most concerned about. We have seen in the past that some people will retweet, repost or forward stuff without regard to its veracity. These are powerful tools that social media puts in the hands of everyone. While almost everyone uses them responsibly, do think twice about what you are hearing or seeing before hitting send. It is important that everyone remain vigilant and correct those who would misinform. If someone says you need to evacuate or boil your water, retweet from the official source, not your neighbor's dentist.

The next couple of days are going to be rough in the East. Facebook and Twitter are going to be valuable resources to keep people informed and in touch with each other, at least as long as they can hit a cell tower or their ISP. But if people clog these channels with half-truths or outright lies, their value is diminished.

It's an old saw, but no less true today: Just because it's on the Internet doesn't make it true.

Nunzsense: A tweet was not the truth

For some reason this story struck a chord with me that a lot of folks either did not recognize or found insignificant. Either way, I thought that while Sam Brownback's staff went overboard, the student was not entirely free of blame since her lie led to everything else. I have fears there will be a lot more of this without media to check out the veracity of claims.

http://www.nvdaily.com/news/2011/12/a-tweet-was-not-the-truth.php