feat: user trust levels #771
Labels
No labels
Bug
Cherry-picking
Dependencies
Documentation
Duplicate
Enhancement
Good first issue
Help wanted
Inherited
Invalid
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Performance
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Unknown
Security
Wont fix
no-priority
old/blocked
old/ci/cd
old/core-matrix
old/database
old/github_actions
old/high-priority
old/low-priority
old/medium-priority
old/question
old/rocksdb
old/rust
packaging
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#771
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?
Discussed here: https://matrix.to/#/!0hQX7RWvN1Bj3twFQR:tomfos.tr/$1spIKgMcjsJ72zD_qVOb8EqjBZgySvTYwVGwp4_ejd0?via=nexy7574.co.uk&via=tomfos.tr&via=explodie.org
"User trust levels" could be a useful tool to allow smaller homeserver deployments to manage new user signups by manually (and automatically?) assigning a trust level to users.
For example, new users could have a trust level of 0, which prevents them uploading media, restricts them to joining a handful of rooms, and may apply some stricter ratelimits.
Then, an admin can increase their trust level (or automatically? after a predetermined number of factors are reached) to lift these restrictions.
Ideally, trust levels would be fully configurable, including what restrictions are placed on each level.