aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| * | More explicit dict indexing Gravatar Leon Sandøy2020-07-24-3/+3
| | | | | | | | | | | | | | | Addresses reviews from MarkKoz Co-authored-by: Mark <[email protected]>
| * | Add sanity to partner and verification check in filtering.py.Gravatar Leon Sandøy2020-07-24-2/+2
| | |
| * | No need for all() in cog_check for AllowDenyLists.Gravatar Leon Sandøy2020-07-24-4/+1
| | |
| * | Put valid_types_list inside the conditional.Gravatar Leon Sandøy2020-07-24-1/+1
| | |
| * | Catch ResponseCodeError in the ValidAllowDenyListType converter.Gravatar Leon Sandøy2020-07-24-7/+7
| | |
| * | Implement new guild invite filtering logic.Gravatar Leon Sandøy2020-07-19-7/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | Validation of guild invites for delete.Gravatar Leon Sandøy2020-07-19-2/+14
| | | | | | | | | | | | | | | We want to support deletion of both IDs and guild invites, so we need a bit of special handling for that.
| * | Validation of guild invites.Gravatar Leon Sandøy2020-07-19-17/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Support the new AllowDenyList field, 'comment'.Gravatar Leon Sandøy2020-07-19-10/+46
| | |
| * | Include the guild ID in mod-log embed.Gravatar Leon Sandøy2020-07-19-3/+4
| | | | | | | | | | | | | | | This gives easier access to the Guild ID in the place where you're most likely to want to use the whitelist command.
| * | Fix an absolutely terrible comment.Gravatar Leon Sandøy2020-07-19-1/+1
| | |
| * | Remove AntiMalWare constants, use cache data.Gravatar Leon Sandøy2020-07-18-55/+30
| | | | | | | | | | | | Also updates the tests for this cog.
| * | Remove Filtering constants, use cache data.Gravatar Leon Sandøy2020-07-18-135/+32
| | | | | | | | | | | | | | | Instead of fetching the guild invite IDs from config-default.yml, we will now be using the AllowDenyList cache to check these.
| * | Add more logging to AllowDenyLists cog.Gravatar Leon Sandøy2020-07-18-2/+11
| | |
| * | Add AllowDenyLists cog.Gravatar Leon Sandøy2020-07-18-0/+145
| | | | | | | | | | | | | | | | | | | | | 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+.
| * | Make the cache more convenient to access.Gravatar Leon Sandøy2020-07-18-1/+13
| | | | | | | | | | | | | | | | | | 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.
| * | Bulletlist with valid file types in converter.Gravatar Leon Sandøy2020-07-18-2/+2
| | |
| * | Better BadArgument exception text.Gravatar Leon Sandøy2020-07-18-2/+3
| | |
| * | Kaizen: Make error_handler.py more embeddy.Gravatar Leon Sandøy2020-07-17-7/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Add ValidAllowDenyListType converter.Gravatar Leon Sandøy2020-07-17-1/+27
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Cache AllowDenyList data at bot startup.Gravatar Leon Sandøy2020-07-17-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Kaizen: Move OffTopicName to converters.py.Gravatar Leon Sandøy2020-07-17-29/+28
| | |
| | * Verification: remove unverified role on acceptGravatar kwzrd2020-08-06-0/+5
| | |
| | * Verification: schedule ping taskGravatar kwzrd2020-08-05-3/+5
| | |
| | * Verification: implement unverified role ping taskGravatar kwzrd2020-08-05-0/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | We're making good use of d.py's tasks framework. RedisCache is used to persist the reminder message ids, which can conveniently be converted into timestamps. It is therefore trivial to determine the time to sleep before the first ping. After that, the bot simply pings every n hours.
| | * Verification: ignore verification reminder message eventGravatar kwzrd2020-08-04-0/+3
| | |
| | * Verification: add reminder cacheGravatar kwzrd2020-08-04-0/+5
| | |
| | * Verification: comment message usesGravatar kwzrd2020-08-04-0/+3
| | |
| | * Verification: add reminder ping message & frequencyGravatar kwzrd2020-08-04-0/+11
| | |
| | * Verification: move time constants above messagesGravatar kwzrd2020-08-04-10/+10
| | | | | | | | | | | | Allows referencing the constants within the message bodies.
| | * Verification: make authorization message ping core devsGravatar kwzrd2020-08-04-2/+3
| | |
| | * Verification: schedule member update taskGravatar kwzrd2020-08-04-1/+12
| | | | | | | | | | | | | | | | | | Turns out that it's necessary to cancel the task manually. Otherwise, duplicate tasks can be running concurrently should the extension be reloaded.
| | * Verification: add region comments & move property to topGravatar kwzrd2020-08-04-4/+17
| | | | | | | | | | | | Cog is getting large so let's allow collapsing related bits.
| | * Verification: create task to update unverified membersGravatar kwzrd2020-08-04-0/+37
| | |
| | * Verification: repurpose & rename `_check_users`Gravatar kwzrd2020-08-04-10/+8
| | | | | | | | | | | | | | | | | | | | | Let's only use this function to check on the guild status. It can be exposed via a command in the future. Name adjusted to be more accurate w.r.t. Discord terminology.
| | * Verification: implement `_verify_kick` helperGravatar kwzrd2020-08-04-0/+63
| | | | | | | | | | | | This will be used to guard the call to `_kick_members`.
| | * Verification: implement `_kick_members` helperGravatar kwzrd2020-08-04-3/+21
| | |
| | * Verification: implement `_give_role` helperGravatar kwzrd2020-08-04-2/+21
| | |
| | * Verification: implement `check_users` coroutineGravatar kwzrd2020-08-04-1/+59
| | | | | | | | | | | | | | | See docstring for details. The coroutine will be registered as a task at a later point.
| | * Verification: define time constantsGravatar kwzrd2020-08-04-0/+3
| | |
| | * Verification: refactor `discord` importsGravatar kwzrd2020-08-04-11/+13
| | | | | | | | | | | | | | | Let's access these via the qualified name. The amount of imported names was starting to get unwieldy.
| | * Verification: add @Unverified role to configGravatar kwzrd2020-08-04-2/+3
| | |
| | * Verification: send initial message on member joinGravatar kwzrd2020-08-02-1/+11
| | |
| | * Verification: adjust & rename welcome messageGravatar kwzrd2020-08-02-3/+3
| | | | | | | | | | | | | | | | | | Let's give it a better name so that it's clear when this message is sent. The initial words are adjusted to avoid repetition after the on join message.
| | * Verification: add initial on join messageGravatar kwzrd2020-08-02-0/+7
| |/ |/| | | | | | | This message will be sent via direct message to each user who joins the guild.
* | Remove superfluous Available help channels.Gravatar Leon Sandøy2020-07-31-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a little bit of logic to the Help Channel `init_available` coroutine, which runs when the cog loads. This ensures that if there are more help channels in available than there should be, we remove the superfluos ones. Previously, if the bot started with too many channels, it would maintain and defend that excessive amount. This is because we never actually count the number of channels before adding in new available channels whenever one disappears. If we ever get too many available channels in the future, this can be solved by simply reloading this cog.
* | Merge pull request #1073 from python-discord/fix/webhook_removerGravatar Leon Sandøy2020-07-30-1/+1
|\ \ | | | | | | Change regex so it catches new discord URL
| * | Use full flag name for case-insensitivityGravatar Senjan212020-07-30-1/+1
| | | | | | | | | | | | requested by lemon
| * | Missed `?` in regex.Gravatar Senjan212020-07-30-1/+1
| | |
| * | Use non-capturing group instead.Gravatar Senjan212020-07-30-1/+1
| | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-26 21:42:49 +0000