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

spam ban app menu command: add right-click App context menu command for spam #504

Open
3 of 8 tasks
JustWaveThings opened this issue Mar 5, 2024 · 1 comment · May be fixed by #548
Open
3 of 8 tasks

spam ban app menu command: add right-click App context menu command for spam #504

JustWaveThings opened this issue Mar 5, 2024 · 1 comment · May be fixed by #548
Labels
Status: In Progress This issue/PR has ongoing work being done

Comments

@JustWaveThings
Copy link
Contributor

JustWaveThings commented Mar 5, 2024

Complete the following REQUIRED checkboxes:

  • I have thoroughly read and understand The Odin Project Contributing Guide

  • The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

The following checkbox is OPTIONAL:

  • I would like to be assigned this issue to work on it
    Along with @Mclilzee.

1. Description of the Feature Request:

Problem: Once a moderator determines that an account is compromised from entries in the automod-block channel, the ban actions and documentation steps are standardized and don't change. It is not too much to do on the desktop app, but it's a bit of a pain on mobile.

Solution: Create a context menu app command as we have for other moderation situations that we would be able to use once we determine an account is compromised.

2. Acceptance Criteria:

  • Mod action: right click or long press on a message from Automod, tap/click on apps, tap/click 'compromised account'
  • Bot action: Bot responds in 'automod-block' with a list of messages from the account that are not in 'automod-block' but recent up to a maximum number of messages, and presents the mod with the option to save messages, not save messages, or cancel.
  • Bot action: Based on the ban option selected, the bot enters the correct command and ban message into 'mod-actions'
  • Mod action: mod selects one of the ban options based on the content not captured in the 'automod-block' channel
  • Bot action: Bot checks and then posts a confirmation that the process succeeded or failed in 'moderation-actions' channel

3. Additional Information:

This command would only be for handling compromised/spam accounts.

@JustWaveThings JustWaveThings added the Status: Needs Review This issue/PR needs an initial or additional review label Mar 5, 2024
@JustWaveThings
Copy link
Contributor Author

We are green-lighted. I'm moving forward with the beginning steps of this @Mclilzee!

@Mclilzee Mclilzee linked a pull request Jun 13, 2024 that will close this issue
7 tasks
@MaoShizhong MaoShizhong added Status: In Progress This issue/PR has ongoing work being done and removed Status: Needs Review This issue/PR needs an initial or additional review labels Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: In Progress This issue/PR has ongoing work being done
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants