Proposal to Reorganize the Moderation Team and Review Moderation Policies

### Is your feature request related to a problem? Please describe. There appears to be a growing level of distrust within the Resonite community toward the current moderation process. Recently, several incidents related to moderation have caused significant concern and discussion within the community. These include cases where worlds that had previously been featured were removed from the public listing in connection with moderation concerns, including at least one case where the delisting action was carried out by a member of the operations team outside of the moderation team. There have also been cases where users were perceived to have received severe moderation actions or bans very suddenly. These situations have raised concerns not only about individual decisions, but also about how moderation-related decisions are made, who is authorized to act on them, and what review or coordination takes place between the moderation team and other members of the Resonite team. I want to be careful not to use this issue to argue whether each individual moderation decision was right or wrong. The moderation team may have access to information or context that is not visible to the wider community. The larger issue, in my view, is that these incidents have caused people to increasingly question the moderation process itself, including: - What criteria are used when making moderation decisions? - Are significant decisions reviewed by multiple people before action is taken? - Is the

Posted by orange3134 on Oct 7, 2026, 3:17 AM

Tags

• github (Other)

Related issues

• struct's lifetime requirements can be bypassed via covariant field assignment
• Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
• proposal: container/...: generic collection types
• Better Custom Endpoint BYOK
• A concrete policy for backward compatibility until Godot 5.0
• New MTP models not supported