Skip to content
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

Closed
Tirokk opened this issue Oct 4, 2020 · 4 comments
Closed

Impose a temporary write lockout on a user for misbehaviour #15

Tirokk opened this issue Oct 4, 2020 · 4 comments

Comments

@Tirokk
Copy link
Member

Tirokk commented Oct 4, 2020

roschaefer Authored by roschaefer
Sep 14, 2018
Closed Feb 18, 2020


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

  • We could restrict the power to admins, not moderators.
  • We could put the button on the admin interface, but moderators have currently no access to it
  • Different strategies as described above

Additional context
screenshot 4

@Tirokk
Copy link
Member Author

Tirokk commented Oct 6, 2020

datenbrei Authored by datenbrei
Mar 27, 2019


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.

@Tirokk
Copy link
Member Author

Tirokk commented Oct 7, 2020

stale[bot] Authored by stale[bot]
Nov 19, 2019


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.

@Tirokk
Copy link
Member Author

Tirokk commented Oct 7, 2020

mattwr18 Authored by mattwr18
Nov 20, 2019


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 ??

@Tirokk
Copy link
Member Author

Tirokk commented Oct 7, 2020

stale[bot] Authored by stale[bot]
Jan 19, 2020


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.

@Mogge Mogge closed this as completed Oct 8, 2020
ulfgebhardt pushed a commit that referenced this issue Feb 15, 2023
…-with-base-and-code

chore: [WIP] 🍰 New Deployment With 'base' And 'code' Docker Images
ulfgebhardt pushed a commit that referenced this issue Jan 28, 2024
feat(frontend): switch TopBar from DefaultLayout to PageShell
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants