From 2a731bf66b2d5813a841c4fd91bd093a0fb888ab Mon Sep 17 00:00:00 2001
From: gnuxie <Gnuxie@protonmail.com>
Date: Fri, 23 May 2025 18:08:47 +0100
Subject: [PATCH] Clarify a comment about the implementation of blocking
 invitations.

---
 src/protections/BlockInvitationsOnServerProtection.tsx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/protections/BlockInvitationsOnServerProtection.tsx b/src/protections/BlockInvitationsOnServerProtection.tsx
index d4b86212..ef3ef38c 100644
--- a/src/protections/BlockInvitationsOnServerProtection.tsx
+++ b/src/protections/BlockInvitationsOnServerProtection.tsx
@@ -36,8 +36,10 @@ export class SynapseHTTPUserMayInvite {
       const serverHash = createHash("sha256")
         .update(userServerName(sender), "utf8")
         .digest("base64");
-      // We only want to block user invites that with recommendation Ban
-      // when they match the automaticRedactReasons.
+      // We only want to block the invitation with user policies with recommendation Ban
+      // when they match the automaticRedactReasons. This is so they can still appeal
+      // being banned in COC use cases.
+      // Server policies are fine to be used to derive the block.
       const matchingUserPolicy = [
         ...this.watchedPolicyRooms.currentRevision.allRulesMatchingEntity(
           sender,