| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is necessary to support walrus operators.
|
| | |
|
| |
|
|
|
| |
Addresses reviews from MarkKoz
Co-authored-by: Mark <[email protected]>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
We now filter guild invites the following way:
- Whitelisted invites are always permitted.
- Blacklisted invites are never permitted.
- If the invite is not blacklisted, it is permitted only if it is a
Verified or a Partnered server, otherwise not.
This strategy was decided on during the June 7th staff meeting, see
https://github.com/python-discord/organisation/issues/261
|
| |
|
|
|
| |
We want to support deletion of both IDs and guild invites, so we need a
bit of special handling for that.
|
| |
|
|
|
|
|
|
|
|
| |
We will now validate and convert any standard discord server invite to a
guild ID, and automatically add the name of the server as a comment.
This will ensure that the list of whitelisted guild IDs will be readable
and nice.
This also makes minor changes to list output aesthetics.
|
| | |
|
| |
|
|
|
| |
This gives easier access to the Guild ID in the place where you're most
likely to want to use the whitelist command.
|
| | |
|
| |
|
|
| |
Also updates the tests for this cog.
|
| |
|
|
|
| |
Instead of fetching the guild invite IDs from config-default.yml, we
will now be using the AllowDenyList cache to check these.
|
| | |
|
| |
|
|
|
|
|
| |
This includes commands to add, remove and show the items in the
whitelists and blacklists for the different list types.
Commands are limited to Moderators+.
|
| |
|
|
|
|
| |
Instead of just dumping the JSON response from the site, we'll build a
data structure that it will be convenient to access from our new cog,
and from the Filtering cog.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, some types of errors are returning plain strings that repeat
the input (which can be exploited to deliver stuff like mentions), and
others are returning generic messages that don't give any exception
information.
This commit unifies our approach around putting as much information as
we can (including the exception message), but always putting it inside
an embed, so that stuff like pings will not fire.
This, combined with the 1.4.0a `allowed_mentions` functionality, seems
like a reasonable compromise between security and usability.
|
| |
|
|
|
|
|
|
| |
We'll use this to ensure the input is valid when people try to whitelist
or blacklist stuff. It will fetch its data from an Enum maintained on
the site, so that the types of lists we support will only need to be
maintained in a single place, instead of duplicating that data in the
bot and the site.
|
| |
|
|
|
|
|
|
|
| |
We shouldn't be making an API call for every single message posted, so
what we're gonna do is cache the data in the Bot, and then update the
cache whenever we make changes to it via our new AllowDenyList cog.
Since this cog will be the only way to make changes to this, this level
of lazy caching should be enough to always keep the cache up to date.
|
| | |
|
| | |
|
| |\
| |
| | |
Update or-gotcha.md
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Invoke fuzzywuzzy's processor before matching
|
| | |\ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | | |
Fixes a regression where the string to be matched was not processed
beforehand.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Trying to match a string with only non-alphanumeric characters
results in a warning by fuzzywuzzy.
Processing the string before matching lets us avoid the warning, which
which uses the root logger and thus isn't supressible.
|
| | | |\
| |_|/
|/| | |
|
| |\ \ \
| | | |
| | | | |
DM relay - minor fixes
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Relay all DMs sent to the bot to #dm_log
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Allow ordering talentpool/bigbrother watched users by oldest added
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
python-discord/bug/info/1050/remove-help-reactions-404
Suppress NotFound when removing help command reactions
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Users can no longer see available channels if they're on cooldown. They
will instead see a special "cooldown" channel which will explain
what's going on.
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The message may be deleted somehow before the wait_for times out.
Fixes #1050
Fixes BOT-6X
|