-
Notifications
You must be signed in to change notification settings - Fork 38
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
Impose a temporary write lockout on a user for misbehaviour #15
Comments
This should be possible for moderators, not admins. Later we possibly could have 2-3 levels of moderation. But it will stay an moderation task. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I guess this is still relevant? has the moderation team brought up any real cases where they would have liked to have been able to impose a temporary writing ban @datenbrei ?? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
…-with-base-and-code chore: [WIP] 🍰 New Deployment With 'base' And 'code' Docker Images
feat(frontend): switch TopBar from DefaultLayout to PageShell
Is your feature request related to a problem? Please describe.
As a moderator, I would like to impose write lockouts on users who conduct misbehavior. If e.g. a user violates our code of conduct, but the misconduct is not bad enough to ban, I could prevent the user from creating posts or commenting on posts. This write lockout could be temporarily. In that case, the timeout could also be accumulative, ie. if a user violates the code of conduct many times, the timeout increases for every violation.
Describe the solution you'd like
As a moderator I want to see a button on the user profile to impose a write lockout. It could be labeled "hold your breath" or sth. similar. After a confirmation the user cannot write posts or comments any more.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: