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

Let the bot handle the Break role #196

Open
mvarendorff opened this issue Feb 7, 2021 · 0 comments
Open

Let the bot handle the Break role #196

mvarendorff opened this issue Feb 7, 2021 · 0 comments
Labels
enhancement New feature or request needs arch input Needs input from the architects regarding specifics

Comments

@mvarendorff
Copy link
Member

mvarendorff commented Feb 7, 2021

Break was solely built as voluntarily picked role so there is no need to worry about potential abuse by people who are timed out. This issue only talks about Break, not Time Out for that reason.

More and more people are taking up on the offer of getting the Break role assigned, removing access to most channels. They later contact moderators to get it removed.

Idea

Implement a !break command that works everywhere. It prompts the user whether they are sure they want the Break role and when confirmed assigns the tag. When the user wants it removed, they can send YesBot a DM and an additional option is included in the DM menu that, when clicked, removes the Break role.

Usage

!break
!menu # in DMs with YesBot, then click the respective icon

Thoughts

  • Is there any reason to save these things in a database? The only thing that comes to mind is the 24 hour limit which was set to prevent people from asking for a Break for 20 minutes. If we can expect sensible use of the command, we can get away with not saving the time. If we can't, we have to to prevent API restrictions because of the flood of channel permission changes the role causes.
  • If we do need a database, it might be worth thinking about adding mod only variants of the command !break @user and !break remove @user to properly modify the database when handing out the role.
@mvarendorff mvarendorff added blocked This issue is blocked by something else; do NOT work on this. enhancement New feature or request labels Mar 2, 2021
@mvarendorff mvarendorff removed the blocked This issue is blocked by something else; do NOT work on this. label Jun 12, 2021
@mvarendorff mvarendorff added the needs arch input Needs input from the architects regarding specifics label Mar 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs arch input Needs input from the architects regarding specifics
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant