Moderation

InfiniTea's Moderation system enables cross-community reporting where servers that share the bot can collaborate on identifying problematic users. When a user is reported in one community, other participating servers can be notified and take appropriate action based on their configured thresholds.

How Cross-Community Moderation Works

The system operates on a shared reporting network:

1. A moderator in Server A reports a user with a category and evidence.
2. Other servers participating in the same report categories receive a notification.
3. Each server independently decides whether to act based on their own configured thresholds.
4. No server is forced to take action. Each community maintains full autonomy over their moderation decisions.

Setup

1. Select report categories: Choose which types of reports your server will monitor and act on (e.g., spam, harassment, raiding, scams). Only reports matching your selected categories will be surfaced to your team.

2. Set the logging channel: Choose a staff-only channel where moderation reports and automated actions will be posted for review.

3. Configure voting thresholds: Set the minimum number of votes (from other servers' moderators) required before a report triggers action in your server. Higher thresholds reduce false positives but may delay response to genuine threats.

4. Define action thresholds: Specify what happens at different severity levels:

   • Warning threshold: Number of reports before a warning is logged.
   • Restriction threshold: Number of reports before the user's permissions are restricted.
   • Ban threshold: Number of reports before an automatic ban is executed.

Important Policies

• Report revocation: Reporters can revoke their report at any time if it was made in error. Revocations reduce the report count and may reverse automated actions.
• Abuse prevention: Abuse of the reporting system (false reports, coordinated targeting) may result in the bot being removed from the offending server.
• Transparency: All moderation actions taken by the bot are logged in your configured channel with full context, allowing staff to review and override if needed.

Best Practices

• Start with conservative thresholds (higher vote counts required) and lower them as you gain confidence in the network.
• Assign a dedicated moderation review channel separate from your general logging channel for better visibility.
• Review automated actions regularly during the first weeks of setup.
• Keep your category selections focused on issues genuinely relevant to your community.
• Communicate to your staff team that cross-community reports exist and how they work.