56. Can block spammer urls and IP addresses, detect repeat postings, check for bad content via custom filters.
57. Use a combination of spam + captcha to rule out most spam comments, contact notifications, anonymous content postings.</li></li></ul><li>Dealing with anonymous users (contrib)<br /><ul><li>Use 3rd party services from contrib.
58. Antispam (http://drupal.org/project/antispam)
59. Validate content against services offered by Akismet, Defensio, or TypePad Antispam where content sent to their servers
60. Comes with a antispam helper module which adds a user role which would allow a user to continue
61. No Supplemental captchas
62. More information at http://www.pixture.com/drupal/node/76
64. Similar to antispam but only works with Mollom servers.
65. Only display a captcha to user if it believes the content to be spam and user not human.</li></li></ul><li>Dealing with anonymous users (contrib)<br /><ul><li>Views Bulk Operations (http://drupal.org/project/vbo)
66. Create views of various types of content (whatever views supports)
67. Provides operations for content (similar to the content list edit page, but much more useful since it uses views).
68. Can update multiple content at once.
69. Used on Drupal.org
70. We will be using it to manage our photo archives. </li></li></ul><li>Registered users<br /><ul><li>Slightly different issue
71. Can post spam via spam bots.
72. Can also spam by hand (children in particular can be VERY persistent)
73. Worry about quality of content (inappropriate content can be a huge concern).
74. Moderating content was a large issue when working on the Zimmer Twins (at the time, over 700k user generated movie clips and over 660k comments – both are over 1M now)
75. Mass spam (by hand) to gain interest in watching their movie clip
76. Trolling other users
77. Inappropriate language and themes.</li></li></ul><li>Dealing with registered users (core)<br /><ul><li>Ability to leave content unpublished until a moderator first looks at the content.
78. Both nodes or comments.
79. Troublesome as you have to click on content to see if there are any issues and work from there.
80. Can also block users.</li></li></ul><li>Dealing with registered users (contrib)<br /><ul><li>Troll (http://drupal.org/project/troll)
81. Block out IP and IP Ranges (has ability to import multiple block lists)
82. Advanced user searching
83. Can be useful in targeting user management
84. Possible solution: use help of users to help with moderating content on site.
85. Flag Content (http://drupal.org/project/flag_content)
86. Ability to flag users, comments, and content
87. User flags can notify an admin who can take a closer look at the content for removal
88. Integration with views to see different parts of content issues.
89. Not been updated in a while…
90. Cannot get more context on why user is flagging content (users sometimes confuse flagging content for abusive reasons as flagging for support)</li></li></ul><li>Dealing with registered users (contrib)<br /><ul><li>Abuse module (http://drupal.org/project/abuse)
91. Written by me
92. Watchlist module
93. Contains list of watchlist and banned regular expressions which automatically flag content if the title, body, content contains pattern.
94. Has moderation section to see content, ability to allow/hide/remove content, give users warnings, ban user.
95. Also has supervisory role to assign content to first level set of moderators.
96. Cannot flag users (though number of warnings, flags user content has received is shown on moderation screen)
97. UI can be daunting.
98. No views support (sorry guys ; its actually broken against views)
99. Code could use a lot of love (now looking for a new maintainer)</li></li></ul><li>Dealing with registered users (contrib)<br /><ul><li>Flag (http://drupal.org/project/flag)
100. Looking like future to moderation problem.
101. Ability to flag content of *any* type
102. Integration with many different projects (views, rules, workflow)
103. Flag Abuse Module (http://drupal.org/project/flag_abuse)
104. Users must provide reasons.
105. Predefined views
106. Integrate with Views Bulk Operations (http://drupal.org/project/vbo) to perform mass operations.
107. Not yet as robust moderator-feature-wise as abuse but some glue (particularly with functionality of watchlist and integration with notifications) could make it much more powerful. </li></li></ul><li>Dealing with registered users (contrib)<br /><ul><li>Revisioning(http://drupal.org/project/revisioning)
109. New ways to ‘manage’ content (can be used in ways of moderation)
110. Really uses workflow module to power moderation of content.
111. Similar issues to flag abuse; how do we get some ideas about the workflow content before we even get to the moderation aspect?</li></li></ul><li>What could mollom do?<br /><ul><li>Mollom actually has a very robust API (see more at http://mollom.com/API)
112. Integrate mollom API to ensure bots are not flagging content.
113. Integrate mollom API to get quality/profanity rating on content and decide if it should be flagged, not allowed, or allowed.
114. Nothing regarding this in contrib quite yet
115. Other options for pre-moderation of content could include using spam or migrating out the watchlist module to work with the above set of solutions.</li></li></ul><li>Working with content editors<br /><ul><li>Sometimes easier (sometimes not).
116. Generally do not have to worry about inappropriate content.
117. May be lower volume of content to check.
118. Different set of problems
119. Inaccurate content.
120. Incorrect links.
121. Expired content.
122. New to Drupal (UI can be a little scary.)</li></li></ul><li>Working with content editors<br /><ul><li>Create new revisions
123. Know who the last content editor was if someone edits content with incorrect information.
124. Check differences between revisions (use the diff module (http://drupal.org/project/diff) to see difference side-by-side).
125. Using revisioning or content moderation might be very useful for publishing content in a proper manner.
126. Use Link Checker? (http://drupal.org/project/linkchecker)
127. Scans links in content and notifies users of any links that do not work.</li></li></ul><li>Working with content editors<br /><ul><li>Could use workflow? (http://drupal.org/project/workflow)
128. Set various states for content to enter
129. Show end user only content that are in certain states.
130. Integrates with views (try to use views bulk operations to manage content en masse).
131. Integrates with flag via rules module or via workflow_flag module.
132. Much easier UI for content editors to understand.</li></li></ul><li>Working with content editors<br /><ul><li>Could use notifications?(http://drupal.org/project/notifications)
133. Notify a set of site content managers when content is created/updated by other content editors.
134. Check to make sure the content is correctly formatted.
135. Use the digest notifications if there is lots of content to avoid a stuffy inbox. </li></li></ul><li>That’s the end!<br /><ul><li>Questions?