Community Security Issues Session 2/ table k

• keeping banned word lists up to date with popculture
• someone in community being stalked by another person in the community (what to do?)
• shoddy design issues will hurt more than help the community
• people who are doing bad things/trolls, these people have to know that the police are going to be involved, that they are responsible for what is happening-- not the website.
• public perception of what is happening onsite is distinctly different from what is actually happening
• kids often are the best signals of who is different
• community empowerment in real life scenarios/community policing/reporting

 -flagging tool

• panic/insecurities in the chatroom

 - what's to be done about other users
 - telling them it's private information

• If somebody was really out of line/hurtful/abusive they would get three strikes of confidential warnings that is up for staffers to see, upon that third strike they are GONE, no more responding/no nothing just get rid of them.

 - secrecy but having a plan about how to deal with them in private

• offensive behavior- create a database/forum that (wiki) keeps the moderator accountable
• what steps are moderators taking

 - have telephone conversation with user that is hurting website
 - customer service/ counseling way to take care of issue
 - direct talk with users may have the best impact (yahoo developer blog)
 - your company is capturing the benefit of these users (community metrics)
 - inbetween users who are different from

• designing something so that someone who is acting badly sees themselves that they are still participating
• appeal process
• no matter how elegant your system is, its how smart the people behind the scenes are.

Key Takeaways:

1) Empower users to control content/trolls
2) Behavior modification is better than outright banning/deleting
3) "Community Policing" is effective
4) Enforced consequences
5) Interstaff (moderator) communication