deploy: 451a9dc7b9

develop/modules/spam_checker_callbacks.html

@@ -216,8 +216,9 @@ this callback.</p>
 <p><em>Changed in Synapse v1.62.0: <code>synapse.module_api.NOT_SPAM</code> and <code>synapse.module_api.errors.Codes</code> can be returned by this callback. Returning a boolean is now deprecated.</em> </p>
 <pre><code class="language-python">async def user_may_invite(inviter: str, invitee: str, room_id: str) -&gt; Union[&quot;synapse.module_api.NOT_SPAM&quot;, &quot;synapse.module_api.errors.Codes&quot;, bool]
 </code></pre>
-<p>Called when processing an invitation. Both inviter and invitee are
+<p>Called when processing an invitation, both when one is created locally or when
-represented by their Matrix user ID (e.g. <code>@alice:example.com</code>).</p>
+receiving an invite over federation. Both inviter and invitee are represented by
+their Matrix user ID (e.g. <code>@alice:example.com</code>).</p>
 <p>The callback must return one of:</p>
 <ul>
 <li>
@@ -251,7 +252,9 @@ this callback.</p>
 ) -&gt; Union[&quot;synapse.module_api.NOT_SPAM&quot;, &quot;synapse.module_api.errors.Codes&quot;, bool]
 </code></pre>
 <p>Called when processing an invitation using a third-party identifier (also called a 3PID,
-e.g. an email address or a phone number). </p>
+e.g. an email address or a phone number). It is only called when a 3PID invite is created
+locally - not when one is received in a room over federation. If the 3PID is already associated
+with a Matrix ID, the spam check will go through the <code>user_may_invite</code> callback instead.</p>
 <p>The inviter is represented by their Matrix user ID (e.g. <code>@alice:example.com</code>), and the
 invitee is represented by its medium (e.g. &quot;email&quot;) and its address
 (e.g. <code>alice@example.com</code>). See <a href="https://matrix.org/docs/spec/appendices#pid-types">the Matrix specification</a>

develop/print.html

@@ -10387,8 +10387,9 @@ this callback.</p>
 <p><em>Changed in Synapse v1.62.0: <code>synapse.module_api.NOT_SPAM</code> and <code>synapse.module_api.errors.Codes</code> can be returned by this callback. Returning a boolean is now deprecated.</em> </p>
 <pre><code class="language-python">async def user_may_invite(inviter: str, invitee: str, room_id: str) -&gt; Union[&quot;synapse.module_api.NOT_SPAM&quot;, &quot;synapse.module_api.errors.Codes&quot;, bool]
 </code></pre>
-<p>Called when processing an invitation. Both inviter and invitee are
+<p>Called when processing an invitation, both when one is created locally or when
-represented by their Matrix user ID (e.g. <code>@alice:example.com</code>).</p>
+receiving an invite over federation. Both inviter and invitee are represented by
+their Matrix user ID (e.g. <code>@alice:example.com</code>).</p>
 <p>The callback must return one of:</p>
 <ul>
 <li>
@@ -10422,7 +10423,9 @@ this callback.</p>
 ) -&gt; Union[&quot;synapse.module_api.NOT_SPAM&quot;, &quot;synapse.module_api.errors.Codes&quot;, bool]
 </code></pre>
 <p>Called when processing an invitation using a third-party identifier (also called a 3PID,
-e.g. an email address or a phone number). </p>
+e.g. an email address or a phone number). It is only called when a 3PID invite is created
+locally - not when one is received in a room over federation. If the 3PID is already associated
+with a Matrix ID, the spam check will go through the <code>user_may_invite</code> callback instead.</p>
 <p>The inviter is represented by their Matrix user ID (e.g. <code>@alice:example.com</code>), and the
 invitee is represented by its medium (e.g. &quot;email&quot;) and its address
 (e.g. <code>alice@example.com</code>). See <a href="https://matrix.org/docs/spec/appendices#pid-types">the Matrix specification</a>