Suggestion: Sticky Mutes

[HarbingerNight]

Mute role should be sticky incase another bot is not used to enforce this. Also need away to unmute members if sticky mute is implemented.

[Benricheson101]

Could you elaborate on what you mean by "sticky mute"?

[HarbingerNight]

I am referring to making the mute role a sticky/persistent role by having the bot reapply GuildConfigs.muteRole to someone who rejoins the server if they were muted by the bot.

Given how aggressive the attacks are getting and the fact it is using hijacked accounts, it is only a matter of time before it is programmed to leave a server and rejoin to clear a mute.

[HarbingerNight]

I forked the project and have mostly finished implementing this and most of the other suggestions sans:

• ignore channel is channel only not categories or threads
• full url in log

It is not pull request ready, but you can take a look to see what Im referring to.
https://github.com/HarbingerNight/anti-phishing-bot/tree/splade/

I also streamlined some stuff.

If you do happen to do anything w/ it please be aware:
It contains an non-destructive advanced migration that preserves existing data for the
schema. If you autogen a new basic one you will need to add instructions on how to handle
existing data, otherwise prisma will try to drop and recreate instead of convert. The migration
file shows how to do this.

https://github.com/HarbingerNight/anti-phishing-bot/blob/splade/prisma/migrations/20211018182540_stickymute/migration.sql

Ive already tested it w/ a database w/ records to make sure it migrates from the current
schema w/ losing data.