aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| | | | | | | * | | Merge branch 'master' into #364-offensive-msg-autodeletionGravatar Matteo2020-03-01-1933/+4045
| | | | | | | |\ \ \
| | | | | | | * | | | Make sure that the offensive message deletion date returned by the API is naive Gravatar Matteo Bertucci2020-02-29-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It could have caused an issue later with a mix of naive and aware datetime Co-Authored-By: Sebastiaan Zeeff <[email protected]>
| | | | | | | * | | | Merge branch 'master' into #364-offensive-msg-autodeletionGravatar Joseph2020-02-02-508/+1333
| | | | | | | |\ \ \ \
| | | | | | | * | | | | Filtering: fix missing deletion date in scheduled task dataGravatar MarkKoz2019-12-15-11/+8
| | | | | | | | | | | |
| | | | | | | * | | | | Filtering: fix comparison between tz naïve and aware datetimesGravatar MarkKoz2019-12-15-1/+1
| | | | | | | | | | | |
| | | | | | | * | | | | Filtering: refactor scheduling of deletion taskGravatar MarkKoz2019-12-15-13/+9
| | | | | | | | | | | |
| | | | | | | * | | | | Filtering: log the status code of caught HTTPExceptionGravatar MarkKoz2019-12-15-4/+2
| | | | | | | | | | | |
| | | | | | | * | | | | Make setting filter.offensive_msg_delete_days pluralGravatar Akarys422019-12-14-2/+2
| | | | | | | | | | | |
| | | | | | | * | | | | Rename route /bot/offensive-message to /bot/offensive-messagesGravatar Akarys422019-12-14-3/+3
| | | | | | | | | | | |
| | | | | | | * | | | | Fix docstring typoGravatar Akarys422019-12-14-1/+1
| | | | | | | | | | | |
| | | | | | | * | | | | Actually schedule message for deletionGravatar Akarys422019-12-14-0/+2
| | | | | | | | | | | |
| | | | | | | * | | | | Catch all HTTPExecptionGravatar Akarys422019-12-14-1/+5
| | | | | | | | | | | |
| | | | | | | * | | | | Rename config entry to offensive_msg_delete_daysGravatar Akarys422019-12-14-3/+3
| | | | | | | | | | | |
| | | | | | | * | | | | Make use of dateutil.parser.isoparseGravatar Akarys422019-12-14-2/+3
| | | | | | | | | | | |
| | | | | | | * | | | | Filtering cog clean upGravatar Akarys422019-12-14-9/+10
| | | | | | | | | | | |
| | | | | | | * | | | | Make use of the Bot subclassGravatar Matteo Bertucci2019-12-12-1/+1
| | | | | | | | | | | |
| | | | | | | * | | | | Merge branch 'master' into #364-offensive-msg-autodeletionGravatar Matteo Bertucci2019-12-12-413/+1442
| | | | | | | |\ \ \ \ \
| | | | | | | * | | | | | Add space for readabilityGravatar Matteo Bertucci2019-12-12-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Co-Authored-By: Mark <[email protected]>
| | | | | | | * | | | | | Merge branch 'master' into #364-offensive-msg-autodeletionGravatar Matteo Bertucci2019-11-16-975/+1910
| | | | | | | |\ \ \ \ \ \
| | | | | | | * | | | | | | Switch to datetime.datetimeGravatar Akarys422019-10-26-6/+6
| | | | | | | | | | | | | |
| | | | | | | * | | | | | | Merge branch 'master' into #364-offensive-msg-autodeletionGravatar Akarys422019-10-25-191/+182
| | | | | | | |\ \ \ \ \ \ \
| | | | | | | * | | | | | | | Use Scheduler instead of a custom async loopGravatar Akarys422019-10-25-41/+43
| | | | | | | | | | | | | | |
| | | | | | | * | | | | | | | Rename offensive_msg flag to schedule_deletion.Gravatar Akarys422019-10-25-7/+7
| | | | | | | | | | | | | | |
| | | | | | | * | | | | | | | Remove the possibility that we send a message to the API that the filter has ↵Gravatar Akarys422019-10-25-15/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | already deleted.
| | | | | | | * | | | | | | | Move offensive message delete time to config file.Gravatar Akarys422019-10-25-2/+4
| | | | | | | | | | | | | | |
| | | | | | | * | | | | | | | Revert whitespace changesGravatar Matteo Bertucci2019-10-25-6/+6
| | | | | | | | | | | | | | |
| | | | | | | * | | | | | | | Autodelete offensive messages after one week.Gravatar Akarys422019-10-25-10/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the filter cog filter a message that's considered as offensive (filter["offensive_msg"] is True), the cog create a new offensive message object in the bot db with a delete_date of one week after it was sent. A background task run every day, pull up a list of message to delete, find them back, and delete them.
| | | | | | | | | | | | | * | Webhook remover: exit early if message already deletedGravatar MarkKoz2020-06-15-2/+8
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | * | Webhook remover: ignore DMs and bot messagesGravatar MarkKoz2020-06-15-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Can't remove messages in DMs, so don't bother trying.
| | | | | | | | | | | | | * | Token remover: exit early if message already deletedGravatar MarkKoz2020-06-15-3/+22
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | * | Token remover: move bot check to on_messageGravatar MarkKoz2020-06-15-21/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It just makes more sense to me to filter out messages at an earlier stage.
| | | | | | | | | | | | | * | Token remover: ignore DMsGravatar MarkKoz2020-06-15-0/+13
| | | | | | |_|_|_|_|_|_|/ / | | | | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's a private channel so there's no risk of a token "leaking". Furthermore, messages cannot be deleted in DMs.
| | | | | | | | | | | | | * Write unit test for `sub_clyde`Gravatar kwzrd2020-06-20-0/+27
| | | | | | | | | | | | | |
| | | | | | | | | | | | | * Preserve empty string when substituting clydeGravatar MarkKoz2020-06-19-0/+2
| | | | | | | | | | | | | |
| | | | | | | | | | | | | * Make sub_clyde case-sensitive and use Cyrillic e'sGravatar MarkKoz2020-06-17-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Cyrillic characters are more likely to be rendered similarly to their Latin counterparts than the math sans-serif characters.
| | | | | | | | | | | | | * Fix 400 when "clyde" is in webhook usernameGravatar MarkKoz2020-06-15-8/+24
| | |_|_|_|_|_|_|_|_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Discord just disallows this name.
| * | | | | | | | | | | | Log exception info for failed attachment uploadsGravatar MarkKoz2020-06-15-1/+1
| | |_|_|/ / / / / / / / | |/| | | | | | | | | |
| * | | | | | | | | | | Add the C# guild to the whitelistGravatar Dennis Pham2020-06-15-0/+1
| | | | | | | | | | | |
| * | | | | | | | | | | Merge pull request #937 from python-discord/bug/filters/928/non-ascii-tokenGravatar Mark2020-06-12-154/+357
| |\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | Make token detection more robust and completely rewrite its tests
| | * \ \ \ \ \ \ \ \ \ \ Merge remote-tracking branch 'origin/master' into ↵Gravatar MarkKoz2020-06-02-1044/+2456
| | |\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bug/filters/928/non-ascii-token
| | * | | | | | | | | | | | Token remover: remove the `delete_message` functionGravatar MarkKoz2020-06-02-19/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's redundant; there's no benefit here in abstracting two lines of code into a function.
| | * | | | | | | | | | | | Test find_token_in_message returns None for invalid matchesGravatar MarkKoz2020-05-28-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This covers the case when a token is matched, but its user ID and timestamp turn out to be invalid.
| | * | | | | | | | | | | | Adjust find_token_in_message tests for the recent cog changesGravatar MarkKoz2020-05-28-19/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It now supports the changes that switched to finditer, added match groups, and added the Token NamedTuple. It also accounts for the is_maybe_token function being removed. For the sake of simplicity, call assertions on is_valid_user_id and is_valid_timestamp were not made.
| | * | | | | | | | | | | | Remove is_maybe_token testsGravatar MarkKoz2020-05-28-33/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The function was removed due to redundancy. Therefore, its tests are obsolete.
| | * | | | | | | | | | | | Add more thorough and realistic inputs for token ID and timestamp testsGravatar MarkKoz2020-05-27-18/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tests for valid inputs and invalid inputs were split to make them more readable.
| | * | | | | | | | | | | | Adjust token remover tests to use the Token NamedTupleGravatar MarkKoz2020-05-27-6/+8
| | | | | | | | | | | | | |
| | * | | | | | | | | | | | Switch findall to finditer in assertionsGravatar MarkKoz2020-05-27-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `find_token_in_message` now uses the latter so the tests should adjust accordingly.
| | * | | | | | | | | | | | Use real token values for testing multiple matches in regexGravatar MarkKoz2020-05-25-3/+4
| | | | | | | | | | | | | |
| | * | | | | | | | | | | | Fix multiple match text for token regexGravatar MarkKoz2020-05-25-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It has to account for the addition of groups. It's easiest to compare the entire string so `finditer` is used to return re.Match objects; the tuples of `findall` would be cumbersome. Also threw in a change to use `assertCountEqual` cause the order doesn't really matter.
| | * | | | | | | | | | | | Fix valid token regex testGravatar MarkKoz2020-05-25-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was broken due to the addition of groups. Rather than returning the full match, `findall` returns groups if any exist. The test was comparing a tuple of groups to the token string, which was of course failing. Now `fullmatch` is used cause it's simpler - just check for `None` and don't worry about iterating matches to search.