aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| | | * | | | 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.
| | | | | | * Change tests to work with the new file layout.Gravatar Numerlor2020-07-15-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 326beebe9b097731a39ecc9868e5e1f2bd762aae
| | | | | | * Move `find_nth_occurrence` to utils helpersGravatar Numerlor2020-07-15-13/+14
| | | | | | |
| | | | | | * Move `send_to_paste_service` to services submoduleGravatar Numerlor2020-07-15-54/+55
| | | | | | |
| | | | | | * Move general helper functions to submodule.Gravatar Numerlor2020-07-15-15/+14
| | | | | | |
| | | | | | * Merge branch 'master' into truncate-internal-evalGravatar Numerlor2020-06-21-492/+1374
| | | | | | |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | # Conflicts: # bot/utils/__init__.py
| | | | | | * \ Merge branch 'master' into truncate-internal-evalGravatar Numerlor2020-05-30-963/+2140
| | | | | | |\ \
| | | | | | * | | Strip empty lines from int eval output.Gravatar Numerlor2020-05-30-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The output generates trailing newlines, which can cause the output to be uploaded to the paste service in cases where it's not needed, as discord will automatically remove those in messages.
| | | | | | * | | Truncate amount of lines in int eval output to 15.Gravatar Numerlor2020-05-30-2/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the amount of newlines was checked and uploaded to the paste service if above 15 but the sent message was not truncated to only include that amount of lines.
| | | | | | * | | Add tests for `send_to_paste_service`.Gravatar Numerlor2020-05-08-0/+74
| | | | | | | | |
| | | | | | * | | Adjust behaviour for new func usage.Gravatar Numerlor2020-05-07-14/+5
| | | | | | | | |
| | | | | | * | | Remove tests from moved function.Gravatar Numerlor2020-05-07-15/+0
| | | | | | | | |
| | | | | | * | | Log unexpected JSON responses.Gravatar Numerlor2020-05-07-0/+4
| | | | | | | | |
| | | | | | * | | continue on internal server errors.Gravatar Numerlor2020-05-07-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the case we receive `"message"` in the json response, the server had an internal error and we can attempt the request again.
| | | | | | * | | Handle broad exceptions.Gravatar Numerlor2020-05-07-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the case an unexpected exception happens, this allows us to try the request again or let the function exit gracefully in the case of multiple fails.
| | | | | | * | | Continue on failed connections.Gravatar Numerlor2020-05-07-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Not using skipping the iteration but continuing directly caused `response_json` being checked but not defined in case of connection errors. Co-authored-by: MarkKoz <[email protected]>
| | | | | | * | | Use new util function for uploading output.Gravatar Numerlor2020-05-06-11/+2
| | | | | | | | |
| | | | | | * | | Handle failed paste uploads.Gravatar Numerlor2020-05-06-1/+6
| | | | | | | | |
| | | | | | * | | Increase log level.Gravatar Numerlor2020-05-06-1/+1
| | | | | | | | |
| | | | | | * | | Send long eval output to paste service.Gravatar Numerlor2020-05-06-0/+10
| | | | | | | | |
| | | | | | * | | Attempt requests multiple times with connection errors.Gravatar Numerlor2020-05-05-12/+17
| | | | | | | | |
| | | | | | * | | Create utility function for uploading to paste service.Gravatar Numerlor2020-05-05-0/+33
| | | | | | | | |
* | | | | | | | | 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
|/ / / / / / / /
* / / / / / / / Disable burst_shared filter of the AntiSpam cogGravatar Sebastiaan Zeeff2020-09-04-4/+9
|/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Our AntiSpam cog suffers from a race condition that causes it to try and infract the same user multiple times. As that happens frequently with the burst_shared filter, it means that our bot joins in and starts spamming the channel with error messages. Another issue is that burst_shared may cause our bot to send a lot of DMs to a lot of different members. This caused our bot to get a DM ban from Discord after a recent `everyone` ping incident. I've decided to disable the `burst_shared` filter by commenting out the relevant lines but leave the code in place otherwise. This means we still have the implementation handy in case we want to re-enable it on short notice. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* | | | | | | Merge pull request #1132 from ↵Gravatar Mark2020-09-03-1/+3
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | python-discord/bug/filters/1130/ignore-codeblock-emoji AntiSpam: ignore custom emojis in code blocks
generated by cgit v1.2.3 (git 2.39.1) at 2025-11-11 17:21:46 +0000