[toc]
Introduction
Spam in release 9.0 is considered abuse and is consolidated into the moderation and abuse workflow. Telligent Community's abuse workflow works using filter plugins help catch, manage, or prevent spam in your community.
Spam business process
While we make diligent effort to catch or prevent spam from the vantage point of our platform, Telligent cannot be held responsible for issues that may occur on networks due to spam-induced or related problems; responsibility for community health and maintenance ultimately rests with your organization's community managers and support team.
You should create a business practice for spam that incorporates your organization's spam practices and responsibilities. The process should at a minimum include the following decisions and action plans:
Decision/Action plan |
Description |
How to monitor for spam | The execution methods might include watching the abuse queue for additions. |
How to identify spam | You might receive user reports about forum posts/comments, blog posts/comments, media gallery posts/comments, wiki posts/comments, or status messages. You might also monitor a user account below a certain age, or use other spam identifiers such as frequency of posting to categorically decide what constitutes abuse. |
What to do with spam | You can use the abuse management queue to review, hide, unhide, or delete spam. |
Who's going to execute the actions | You need to have assigned roles for abuse management. One of these roles might be a blog or forum/media gallery moderator, who reviews content and allows it or disallows it. You might have other roles who would participate in this process. |
Frequency of execution | You need to decide how frequently you're going to check efficacy of abuse practices and how often abuse will be reviewed. |
Efficacy evaluation | Create measures for the efficacy of your tools. |