feat: account suspension #766

New issue

Closed

opened 2025-04-16 19:34:33 +00:00 by nex · 2 comments

nex commented

2025-04-16 19:34:33 +00:00

Owner

Account suspension is less effective than locking, so if we do end up implementing these, locking should ideally be priorities over suspension - clients losing state isn't much of a concern when most of them have a way to perform a new initial sync anyway.

While we can already deactivate accounts in a way that effectively locks them, however, if there is no way to contact the locked user out-of-band to supply them with a new password, there is no way to "unlock" the account in a way that allows it to be used again. Account suspension is less effective than locking, so if we do end up implementing these, locking should ideally be priorities over suspension - clients losing state isn't much of a concern when most of them have a way to perform a new initial sync anyway.

nex added the

Enhancement

Matrix/Administration

Matrix/Auth

labels

2025-04-16 19:34:33 +00:00

nex changed title from ~~feat: account locking and suspension~~ to feat: account suspension

2025-06-24 21:22:30 +00:00

nex commented

2025-06-24 21:24:21 +00:00

Author

Owner

When implementing, a synapse-compatible HTTP endpoint will also likely be added to allow moderation bots like Draupnir and Meowlnir to automatically issue suspensions for users who wind up on policy lists.

Locking is being dropped from the scope of this issue because most admins I've spoken to have assessed that suspension is generally the desired course of action instead of locking, since locking is basically just non-nuclear deactivation (which we already support), whereas suspension basically just makes users read-only and has minimal affect on a legitimate user if they are accidentally suspended and later unsuspended. When implementing, a synapse-compatible HTTP endpoint will also likely be added to allow moderation bots like Draupnir and Meowlnir to automatically issue suspensions for users who wind up on policy lists.

nex commented

2025-08-21 15:47:47 +00:00

Author

Owner

closed by #876, the HTTP endpoint will be added by whatever PR closes #922

nex closed this issue

2025-08-21 15:47:47 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: continuwuation/continuwuity#766

No description provided.

Rows
Columns