Port spam-checker API callbacks user_may_join_room, `user_may_invit…

…e`, `user_may_send_3pid_invite`, `user_may_create_room`, `user_may_create_room_alias`, `user_may_publish_room`, `check_media_file_for_spam` to more powerful and less ambiguous `Union[Literal["NOT_SPAM"], Codes]`. This is a followup to #12703, #12808, #12846 and builds towards giving the spam-checker API the ability to inform users of *why* their event or operation has been rejected. WIP: Applying feedback.
matrix-org · Jun 6, 2022 · 8166bd5 · 8166bd5
1 parent a376e60
commit 8166bd5
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/changelog.d/12857.feature b/changelog.d/12857.feature
@@ -1 +1 @@
-Port spam-checker API callbacks `user_may_join_room`, `user_may_invite`, `user_may_send_3pid_invite`, `user_may_create_room`, `user_may_create_room_alias`, `user_may_publish_room`, `check_media_file_for_spam` to more powerful and less ambiguous `Union[Literal["NOT_SPAM"], Codes]`. This is a followup to #12703, #12808, #12846 and builds towards giving the spam-checker API the ability to inform users of *why* their event or operation has been rejected.
+Port spam-checker API callbacks to a new, richer API. This is part of an ongoing change to let spam-checker modules inform users of *why* their event or operation has been rejected.