It’s the end of our first week on business at TBD and, admittedly, I’m completely exhausted. We all are.
It felt like a good first week for us – we got a lot of reviews, positive and negative, from other media sites and blogs. Despite the bugs and occasional complaints, we did have the opportunity to come out of the gates with a few engagement experiments you might find helpful at your own news orgs.
Open discussion on launch day
We had an open Cover it Live chat on the Community Blog from 9-4 on launch day. TBD Community hosts Lisa Rowan, Jeff Sonderman, Daniel Victor and Nathasha Lim took questions, complaints and bug reports from site visitors in an open and honest fashion. They didn’t just address the positive, they also did what they could to assuage the fears of those missing the former websites for WJLA and News Channel 8, now replaced by TBD.com.
Crowdsourcing for breaking news photos
On Thursday, the Washington, D.C. area woke up to severe thunderstorms, high winds, flooding streets – and a lot of damage. While our one full-time photographer was able to get a lot of art, we knew we couldn’t be everywhere. The call was sounded for photos on Twitter and on the site – and readers responded with submissions on-site and via Twitpic.
We ended up repeating this process later in the day with a reported electrical fire near the District’s business center. I first saw reports and Twitpics of the fire on a random Twitter search for “Fire near: Washington DC”. We quickly reached out on Twitter for permission to use the photos – and we were off to the races. It was great to get such good response out of the gate.
Working with bloggers on breaking news
Around 1:30 pm Tuesday, I looked over one of my series of Twitter searches and found a tweet reporting an alleged hit-and-run by a Metrobus in Arlington, Va. I contacted the guy, Matt, via reply and asked him if he’d talk to our Arlington reporter, Rebecca Cooper. He agreed.
At 2:12, network partner site Unsuck DC Metro, who the original tweet was directed toward, had a post up with the tip.
Another partner site, ARLNow, had a story with photos and quotes from the man involved in the accident at 3:07. TBD had a story with the tipster’s report and ARLNow’s report up before 4 p.m, approximately four hours before The Washington Post or WTOP (and a hat tip to the Post for promoting the great efforts of ARLNow).
Without the tip provided by Twitter and the hustle by the bloggers in our community network, there’s no way we could have had such a story so fast. Who says bloggers aren’t journalists? Not us.
Tapping into the crowd for political coverage
On Wednesday, TBD TV’s Newstalk program had the Democratic candidates for D.C. mayor on the program for a debate. In the hours before the 10 a.m. debate, we asked readers to submit their questions for the candidates via hashtag on Twitter. The response was more than we could fit on the program, which was great (see right).
When the debate went live on TV and online, fact-checking reporter Kevin Robillard had a live Cover it Live chat where readers could chime in with comments, ask questions and suggest facts to be checked as the candidates said them on the air.
The debate got a lot of traction on Twitter and on the chat. Kevin had some great material for The Facts Machine, which is a TBD blog dedicated to backing up or refuting questionable facts.
We hope to do a lot more projects like this in the future. Not bad for the third day out.
Anonymity isn’t to blame for bad site comments, it’s a lack of staff interaction
By Mandy
On March 23, 2010
In Industry News & Notes, Rants
A Twitter discussion I glimpsed Sunday – and follow-up blog post and discussion about it from Steve Buttry – has had me thinking a lot about anonymous commenting on news sites yesterday. Of course, a lot of that also comes from the fact that I returned from a week-long furlough to moderate comments on the morning after the health care reform bill passed (I don’t know what the mood is like where you are, dear reader, but it’s pretty heated here in Southwest Ohio).
As I’ve written here before, it is part of my job to navigate the waters of Cincinnati.Com’s article and blog comments to determine what should stay and what gets removed as per our terms of service. Back in 2008, I helped set up the site’s comment system, wrote our discussion guidelines and laid the groundwork for how comments would be moderated. The process has evolved and grown to keep up with what we’ve learned from interacting with and watching our community members – and it’s given me a unique perspective on anonymity and commenting.
Of all the comments I’ve removed and all the users I’ve had to block from our sites, I’ve learned a few things that have led me to believe that anonymity doesn’t really matter at all. Here’s why:
1. Most users who have had comments removed do not believe their comment was racist/homophobic/libelous/spam – and they would see no problem posting that comment again (and again) under their real names.
2. Most users who have comments removed or are kicked off the site have no problem contacting staff by phone or email to complain, thus dropping their anonymity in most cases. Aside: The tops is when they use a work email address to defend their statements about how “X race is too lazy to work”. Hilarity.
3. Banned or unverified users will find a way to post what they want to post. Whether it is creating a fake Facebook/OpenID identity, a new IP address, dozens of Hotmail addresses, cleaned cookies – they’ll do it to get around a login system. There are about five users I have kicked off our site dozens of times – and there’s seemingly nothing I can do to get them to go away permanently. One even went so far as to tell me, “Do what you want. I have nothing but time on my hands – and you don’t.”
On the flip side, I am a longtime member of a message board that has very few of these problems. The site’s thousands of users know and respect one another for the most part, conversations stay on-topic and free of hate speech and I rarely see users or comments removed. What’s their secret? Constant moderator interaction.
A moderator is always online -and there is an indication of this that shows up on the forum. The moderator regularly participates in discussion, responds to questions and, most importantly, will give warnings publicly when they are needed. It’s not uncommon to see a gentle “Hey guys let’s try to get this back on topic” or “I had to remove a few posts that got pretty heated, try to keep it civil, folks”. Sometimes the moderators don’t even have to do this. Other members will band together to fight off a troll – or defend a friend they feel was wronged. This sense of community derives from the understanding that there’s safety and support supplied by that moderator presence.
Contrast this with the moderator involvement on most news sites. Most users don’t even know a staffer was reading their comments until they are removed. Chances are most users don’t know a site’s moderators until they get a warning. We all know what the solution is, but our paper – and most other sites like ours – is not able to put that amount of manpower into moderation. Community interaction is not a top-level priority to most news outlets – and that’s the real problem.
We as an industry like to collectively wring our hands about the toxicity of online comment boards, but if we really want to improve the quality of on-site discussion we need to be willing to get involved in our sites in a hands-on manner. No amount of word filters, comment-detecting robots and user-end moderation will replace the presence of a dutiful moderator (and that, unfortunately, requires money).