Automating Alerts from MediaWiki Recent Changes with Extensions

Best Practices for Reviewing MediaWiki Recent Changes Efficiently

1. Configure filters and watchlists

• Use namespaces and page filters: Limit Recent Changes (RC) to relevant namespaces (e.g., Main, Talk) to reduce noise.
• Set minimum change sizes and hide minor edits to skip trivial edits.
• Maintain focused watchlists: Encourage users to add high-priority pages to personal watchlists for targeted monitoring.

2. Use user and tag filters

• Exclude bots or specific users if their edits are routine and trusted.
• Leverage abuse filters and tags: Highlight or tag edits that match problematic patterns, and filter RC by those tags.

3. Employ extensions and tools

• Enable FlaggedRevs or ConfirmEdit where appropriate to require review before publication.
• Use AbuseFilter and SpamBlacklist to auto-detect and prevent common vandalism.
• Install RecentChangesPager, Echo (notifications), or external monitoring tools for enhanced sorting, paging, and alerts.

4. Set up notifications and alerts

• Use Echo notifications to notify reviewers about changes to watched pages or pages needing attention.
• Integrate with external alerting (email, chatops, or webhook) for critical namespaces or high-traffic wikis.

5. Create a triage workflow

• Triage categories: e.g., urgent (vandalism, policy violations), review (content changes), informational (minor/formatting).
• Assign roles: designate on-duty reviewers and escalation pathways for contentious edits.
• Document response times and SLAs for different categories to ensure consistent handling.

6. Use visual and diff aids

• Enable visual diffs to make it quicker to spot meaningful content changes.
• Customize diff context (number of lines) to balance scope and speed when reviewing larger edits.

7. Train reviewers and maintain guidelines

• Provide concise reviewer checklists for common issues (vandalism cues, copyright, POV).
• Run periodic refresher sessions and keep documentation up to date.

8. Automate repetitive actions

• Use bots for rollback of clear vandalism and to revert common spam patterns.
• Script batch tasks (tagging, patrol marking) to reduce manual work.

9. Monitor metrics and iterate

• Track metrics: time-to-first-review, number of reverts, false positives/negatives.
• Regularly review workflows and tweak filters, alerts, and team assignments based on metrics.

10. Security and access control

• Limit rollback/patrol permissions to trusted users.
• Audit account activity for suspicious patterns and enforce strong account policies.

If you want, I can produce a one-page reviewer checklist, a sample watchlist configuration, or specific filter strings for your wiki—tell me which.