-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement allowlist and blocklist #120
Implement allowlist and blocklist #120
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the work, very nice PR over all. One suggestion for a small change and another point open for discussion. :)
I will now test the implementation more thoroughly and remove the WIP tag when I'm done testing. |
(CI failing on python 3.12 is expected: #112) |
Seems to be working as expected. Good to merge from my side. (: |
This PR implements both allowlisting and blocklisting regexes of MXIDs.
I have not completely tested these changes yet, this is still a draft version to allow the maintainers to do an initial review and request changes before I do final testing.
@HarHarLinks What do you think? I'm still thinking about whether or not the bot should respond with an error message when receiving a message from a disallowed user. Especially with open issues of the bot spamming duplicate responses to old messages, I personally think we should just drop the events without any response. But this may be bad UX for accidentally disallowed users.