| Commit message (Collapse) | Author | Lines | 
 | 
Remove the moderator notification when unloading the cog because. Its
purpose was to remind to manually unsilence channels. However, this
purpose is now obsolete due to automatic rescheduling.
The notification was buggy anyway due to a race condition with the bot
shutting down, and that'd be further complicated by having to
asynchronously retrieve channels from the redis cache too.
Fixes #1053
 | 
 | 
Can be used to support rescheduling.
 | 
 | 
It was confusing to reject a silence and an unsilence when overwrites
were manually set to False. That's because it's contradictory to show
an error stating it's already silence but then reject an unsilence with
an error stating the channel isn't silenced.
 | 
 | 
Admins will have to manually check the default values used and adjust
them if they aren't the desired values for that particular channel.
 | 
 | 
Overwrites can be edited during a silence, which can result in the
overwrites check failing. Checking the scheduler too ensures that
a duplicate silence won't be scheduled.
 | 
 | 
No longer assume default values for the overwrites which are modified.
Save and restore previous values `add_reactions` and `send_messages`
via redis.
When unsilencing, check if a channel is silenced via the redis cache
rather than the channel's current overwrites to ensure the task is
cancelled even if overwrites were manually edited.
 | 
 | 
See issue #1101
 |