Restrict actions on specific users #42
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are users managed by bridges/appservices/bots - such users must not be deactivated/erased, passwords for them must not be changed, devices must not be removed, etc. Basically, the only 2 things that may be changed for those users are the avatar and display name
Please add a config option like
asManagedUsersthat will accept list of regexes for the MXIDs that managed by application services (bridges). Here is an example how such regexes are defined (syntax can be different, not a big deal): https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml#L209Fixes #36