aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| | | | | | * | Merge remote-tracking branch 'upstream/master' into smart_syncing_usersGravatar RohanJnr2020-09-21-257/+301
| | | | | | |\ \
| | | | | | * | | refactor code to GET users from site endpoint `bot/users` with paginationGravatar RohanJnr2020-09-21-1/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added method to recursively GET users if paginated and another method to parse URL and return endpoint and query parameters.
* | | | | | | | | Add voice gate configuration to config-default.ymlGravatar ks1292020-10-10-0/+6
| | | | | | | | |
* | | | | | | | | Define Voice Gate channel, role and requirement in constants.pyGravatar ks1292020-10-10-0/+10
| | | | | | | | |
* | | | | | | | | Create base Voice Gate cogGravatar ks1292020-10-10-0/+15
| |/ / / / / / / |/| | | | | | |
* | | | | | | | PR #1151 Sync: remove confirmationGravatar kwzrd2020-09-26-519/+24
|\ \ \ \ \ \ \ \ | |/ / / / / / / |/| | | | | | |
| * | | | | | | Sync: update sync() docstringGravatar MarkKoz2020-09-26-3/+1
| | | | | | | |
| * | | | | | | Sync: remove _asdict commentGravatar MarkKoz2020-09-23-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The comment doesn't contribute anything.
| * | | | | | | Merge branch 'master' into feat/backend/1075/remove-syncer-confirmGravatar MarkKoz2020-09-22-2227/+2207
| |\ \ \ \ \ \ \
| * | | | | | | | Sync: refactor conditional for sending message Gravatar Mark2020-09-22-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ternary is a bit confusing. Co-authored-by: Numerlor <[email protected]>
| * | | | | | | | Fix test for sync message being editedGravatar MarkKoz2020-09-07-1/+3
| | | | | | | | |
| * | | | | | | | Sync: remove confirmationGravatar MarkKoz2020-09-07-518/+20
| | |_|_|/ / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The confirmation was intended to be a safe guard against cache issues that would cause a huge number of roles/users to deleted after syncing. With `wait_until_guild_available`, such cache issue shouldn't arise. Therefore, this feature is obsolete. Resolve #1075
* | | | | | | | Merge pull request #1161 from bast0006/feature-bast-user-token-notifyGravatar Mark2020-09-25-39/+188
|\ \ \ \ \ \ \ \ | |_|_|_|_|_|_|/ |/| | | | | | | Add userid decoding and user token detection to the token removal moderation feature
| * | | | | | | Remove redundant is_valid_userid functionGravatar Bast2020-09-25-33/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | extract_user_id(id) is not None does the same job and is not worth the extra function
| * | | | | | | Change the mod alert message component for the user token detectionGravatar Bast2020-09-24-46/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clean up mock usage, docstrings, unnecessarily split-lined function calls
| * | | | | | | Add BOT vs USER token detection, properly handling bot tokens for bots in ↵Gravatar Bast2020-09-24-13/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the current server Also adjust the naming and purposes of the format messages to KNOWN and UNKNOWN token messages.
| * | | | | | | Implement review-suggested changesGravatar Bast2020-09-24-67/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | userid -> user ID maybevalid -> maybe_valid remove collections import and added a new function that handles the "format user ID log message" and should_ping_everyone feature
| * | | | | | | Merge branch 'master' into feature-bast-user-token-notifyGravatar Bast2020-09-21-270/+686
| |\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | Resynchronize changes with the new cog folder arrangement
| * | | | | | | | Make token_remover check basic HMAC validity (not low entropy)Gravatar Bast2020-09-19-6/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Handles cases like xxx.xxxxx.xxxxxxxx where a user has intentionally censored part of a token, and will not consider them "valid"
| * | | | | | | | Add feature to token_remover: log detected user ID, and ping if it's a user ↵Gravatar Bast2020-09-19-19/+90
| | |_|_|_|_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in the server Updated tests This comes with a change that a user ID must actually be able to be decoded into an integer to be considered a valid token
* | | | | | | | Merge pull request #1171 from python-discord/kwzrd/log-levelsGravatar Mark2020-09-23-2/+2
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | Adjust verification & incidents log levels
| * | | | | | | | Incidents: bump archive log to INFO levelGravatar kwzrd2020-09-23-1/+1
| | | | | | | | |
| * | | | | | | | Verification: reduce request dispatch log levelGravatar kwzrd2020-09-23-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid information duplication in production logs.
* | | | | | | | | Fix use of expanded infraction response for usernameGravatar MarkKoz2020-09-23-1/+1
|/ / / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | Fixes BOT-9A
* | | | | | | | Update format_user to remove username and add IDGravatar Joe Banks2020-09-23-4/+2
| | | | | | | |
* | | | | | | | Clean: fix mention in mod log messageGravatar MarkKoz2020-09-22-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes BOT-99
* | | | | | | | Avoid using discord.Object's repr as the username for infraction searchGravatar MarkKoz2020-09-22-0/+7
| | | | | | | |
* | | | | | | | Fix AttributeError for infraction user searches via the groupGravatar MarkKoz2020-09-22-1/+1
| | | | | | | |
* | | | | | | | Fix future date check in snowflake converterGravatar MarkKoz2020-09-22-1/+1
| | | | | | | |
* | | | | | | | Merge pull request #1126 from ↵Gravatar Mark2020-09-22-37/+22
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | python-discord/feat/info/1125/user-cmd-whitelist-modmail Whitelist the modmail category for displaying verbose infraction info from the user command
| * \ \ \ \ \ \ \ Merge branch 'master' into feat/info/1125/user-cmd-whitelist-modmailGravatar MarkKoz2020-09-22-3054/+2635
| |\ \ \ \ \ \ \ \ | |/ / / / / / / / |/| | | | | | | |
* | | | | | | | | Merge pull request #1061 from python-discord/feat/frontend/533/mod-log-namesGravatar Mark2020-09-22-207/+209
|\ \ \ \ \ \ \ \ \ | |_|_|_|_|/ / / / |/| | | | | | | | Use mentions for users in mod logs and infraction search results
| * | | | | | | | Filtering: add missing space to log msgGravatar Mark2020-09-22-1/+1
| | | | | | | | |
| * | | | | | | | Fix type annotation for expanded infractionsGravatar MarkKoz2020-09-22-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `_utils.Infraction` alias does not cover nested data structures. Therefore, it's inappropriate for expanded infraction API responses.
| * | | | | | | | Merge branch 'master' into feat/frontend/533/mod-log-namesGravatar MarkKoz2020-09-22-3016/+2690
| |\ \ \ \ \ \ \ \ | |/ / / / / / / / |/| | | | | | | |
* | | | | | | | | Merge pull request #1168 from python-discord/feat/latencyGravatar Senjan212020-09-22-1/+69
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | Latency cog for checking ping.
| * \ \ \ \ \ \ \ \ Merge branch 'master' into feat/latencyGravatar Xithrius2020-09-22-1463/+224
| |\ \ \ \ \ \ \ \ \ | |/ / / / / / / / / |/| | | | | | | | |
* | | | | | | | | | Merge pull request #1163 from ↵Gravatar Sebastiaan Zeeff2020-09-22-843/+168
|\ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | python-discord/sebastiaan/features/use-async-rediscache-package Use `async-rediscache` package for our redis caches
| * \ \ \ \ \ \ \ \ \ Merge branch 'master' into sebastiaan/features/use-async-rediscache-packageGravatar Sebastiaan Zeeff2020-09-22-1136/+1003
| |\ \ \ \ \ \ \ \ \ \ | |/ / / / / / / / / / |/| | | | | | | | | |
* | | | | | | | | | | Merge pull request #1164 from python-discord/sebastiaan/bugs/duckpondGravatar Dennis Pham2020-09-21-630/+102
|\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Several improvements to duckpond
| * | | | | | | | | | | Use `has_any_role` decorator instead of old `with_role` decoratorGravatar Den42002020-09-21-2/+2
| | | | | | | | | | | |
| * | | | | | | | | | | Merge branch 'master' into sebastiaan/bugs/duckpondGravatar Den42002020-09-21-506/+901
| |\ \ \ \ \ \ \ \ \ \ \ | |/ / / / / / / / / / / |/| | | | | | | | | | |
* | | | | | | | | | | | Merge branch 'bug/1142/fix-everyone-ping' into masterGravatar Daniel Brown2020-09-21-62/+47
|\ \ \ \ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ \ \ \ Merge branch 'master' into bug/1142/fix-everyone-pingGravatar Kieran Siek2020-09-19-88/+808
| |\ \ \ \ \ \ \ \ \ \ \ \ | | | |_|_|_|_|/ / / / / / | | |/| | | | | | | | | |
| * | | | | | | | | | | | Add everyone_ping filter.Gravatar kosayoda2020-09-08-11/+47
| | | | | | | | | | | | |
| * | | | | | | | | | | | Remove everyone_ping rule from antispam.Gravatar kosayoda2020-09-07-152/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The feature will be moved to the filtering cog.
| * | | | | | | | | | | | Add test for everyone_ping rule.Gravatar kosayoda2020-09-05-0/+102
| | | | | | | | | | | | |
| * | | | | | | | | | | | Detect pings after removing codeblocks.Gravatar kosayoda2020-09-05-6/+9
| | | | | | | | | | | | |
| | | * | | | | | | | | | Lower duckpond threshold to increase activityGravatar Sebastiaan Zeeff2020-09-20-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There's not a lot of activity in our duckpond at the moment. To activate our duckies, I've decreased the duckpond threshold to 4. This means that a message will now be relayed once it's been ducked four times. Let's get all of our ducks in a row. Signed-off-by: Sebastiaan Zeeff <[email protected]>
| | | * | | | | | | | | | Add command to relay a message to duckpondGravatar Sebastiaan Zeeff2020-09-20-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds a command that allows admins to manually relay a message to the duckpond, regardless of duck counts and the checks done in the reaction event handler. Signed-off-by: Sebastiaan Zeeff <[email protected]>
generated by cgit v1.2.3 (git 2.39.1) at 2025-11-02 06:50:55 +0000