Default room ACLs #775
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#775
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add a configuration option to set a default ACL for rooms created on the homeserver.
This should come with a big warning to say that these ACs will not be automatically updated, and are not a substitution for moderation bots.
See also: #774 (comment)
This issue has been posted to This Week in Rust's Call for Participation. If you're new to the project, check out the contributing guide. Welcome!
Given the client can specify additional initial state events when creating a room, this could be as simple as appending/adding a default
m.room.server_acl
event.There could be a config option such as
default_acl_deny
, which is just an array of patterns to exclude, anddefault_acl_allow
which does the inverse. It's worth mentioning that deny overrides allow, so the two options should probably be mutually exclusive.