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.

Yoric · Yoric · commit 8166bd58ea47 · 2022-06-06T15:55:06.000+02:00
WIP: Applying feedback.
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.

Original file line number	Diff line number	Diff line change
`@@ -1 +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.
	`1`	`+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.`