Follow up: The vulgar comment & the school
Cross-posted from The Editors’ Desk on STLtoday.com.
As you can imagine, we’ve watched the uproar closely in the wake of my blog post on Monday. I recounted the case of a person who lost his job at a local school after twice posting a vulgar comment on the Talk of the Day blog on Friday.
We don’t condone vulgarity or obscenity on our site. We won’t tolerate it. Increasingly, we are concerned about the tone of the conversation on STLtoday. When we can, we ban people without apology for bad behavior. We have taken steps to beef up our review process and we’ll continue to enhance those measures to address bad language and intolerant speech.
We also miss stuff, so we depend on you to point out those comments and help us deal with them. That’s not new; we’ve said that from the beginning. We want to hear from you.
On Friday, I saw the reader’s comments, I noticed the comments came from a school and I made the decision to call. The school used its server logs to track the comments, based on the time they were made, to a single work station. After confronting the employee, he resigned. Since then, I’ve heard the criticism, loud and clear.
The criticism of me falls largely in four categories. First, that I overreacted, using an atomic fly-swatter to address the issue. Second, that I somehow violated our privacy policy. Third, that I’ve set some sort of precedent for how we deal with readers who make obscene comments. And fourth, that I was gleeful or boastful in blogging about the incident in the first place.
In the wake of a few days of reflection, I would like to clear up some misinformation and offer some thoughts on what I’ve learned from this episode.
Did I reveal private information? No. I had none to reveal and wouldn’t have if I had it. From me, the school learned three things: 1) That the comments were posted; 2) When the comments were posted; 3) That I knew they came from the school based on the DNS information that accompanied the IP address. The school knows its own IP address. Knowing when the comments were posted allowed them to track them to a specific work station through its own server logs.
Could I have simply banned the reader? Perhaps, but not reliably. Our blogs don’t require registration for reader comments. He used a fake e-mail address. There wasn’t a way on Friday to reliably prevent him from commenting.
Could I have banned the IP address? Yes, but that would have prevented anyone from the school from visiting our site. That’s a step we preferred not to take.
Did I “hunt someone down” after seeing the comments? No. There was no “sleuthing” involved. The name of the school was readily visible on the e-mail alert about the comment.
Was I gloating about this incident? That wasn’t my intention. And I regret that it sounded like I was. I intended to simply explain to readers a step I’d tried to help rein in the vulgarity. I was utterly surprised by the reaction.
Have I set some sort of precedent for STLtoday? We don’t routinely, and would not routinely take the steps I took in this case. For particularly bad cases of abusing our guidelines with vulgarity and obscenity, we would not rule it out.
Did I overreact? Maybe I did. I am constantly frustrated by the difficulty of dealing with this kind of language. And in this case, I was motivated by three things.
First, this came from a school. I didn’t know if it came from an employee, a guest or a student. But I viewed it as a “teachable moment” and a chance, perhaps, to nip something in the bud, to engage the community to help me. I didn’t anticipate that the reader would resign.
Second, the comment was posted, deleted and intentionally posted a second time by the same person. Too much time had elapsed between posts for it to be a mistake or an accident. The reader was determined to post it.
Third, it was easy. As I said, I didn’t have to dig for the school’s information. It was readily available on the e-mail alert. Had it not been there, I may have deleted the comment and moved on.
A few things I’ve learned from this episode:
I should have walked the idea around the newsroom a little more before calling the school. I was motivated by the fact that it was a school. We may have decided to try something less drastic. We may have done exactly the same thing. I couldn’t know without asking.
I should take pains to measure my language carefully. As I said, I hadn’t intended to display glee over this incident. Some of my language in an early version of the blog item and some Twitter remarks was not consistent with my intention.
This isn’t new, but it reinforces what I have always known: Your trust is paramount. I did not and would not violate our privacy policy. I regret that this episode may have cast doubt on that. We take our privacy policy seriously.
We also take seriously our responsibility to monitor conversation on STLtoday. We know there is more we can do, operationally and technologically to improve. We’ve already talked about how and when to escalate our response to bad language.
My colleagues and I agree we are committed to working as hard as we can to foster and encourage discussion on STLtoday. That means taking a measured approach to consider any and all steps — within our policies — to put a stop to it or eliminate it when we see it.
Related Posts:
Comments
-
Paul N.
-
Mr. Geek
-
Bill
-
cmgrantham
-
Norman
-
Joanne
-
rich727
-
Brian Schwartz
-
GaryB
-
tom
-
SN
-
Paul
-
Mr Magority.
-
Guest
-
Tom
-
Jenniferwhatnot
