| Commit message (Collapse) | Author | Lines | ||
|---|---|---|---|---|
| 2019-09-25 | Add all the shields |  scragly | -3/+7 | |
| 2019-09-24 | Remove repeat logic for off-topic-name api call |  Sebastiaan Zeeff | -6/+1 | |
| After a short discussion in the core-dev team, we decided to not use retry logic for a failed API call for new off-topic-names. We may introduce something similar in the future, but we're not sure on the direction we want to take yet. | ||||
| 2019-09-25 | Remove unnecessary sudo for pipenv install. | scragly | -1/+1 | |
| 2019-09-24 | Fix reminders filter query |  S. Co1 | -2/+2 | |
| Closes #445 | ||||
| 2019-09-25 | Remove regex wheel as dateparser is no longer used. | scragly | -0/+0 | |
| 2019-09-24 | Put import in alphabetical order |  Matteo Bertucci | -1/+1 | |
| 2019-09-24 | Override waiting time to half an hour | Matteo Bertucci | -1/+6 | |
| If an exception occurred | ||||
| 2019-09-24 | Fix importing error | Matteo Bertucci | -1/+2 | |
| `bot.api.ResponseCodeError` is now imported | ||||
| 2019-09-24 | Prevent false-positives of the rich embed filter | Sebastiaan Zeeff | -15/+33 | |
| https://github.com/python-discord/bot/issues/293 The rich embed filter is plagued by false positives now Discord has added more custom preview embeds for various websites. Since these embeds have the `rich` type instead of the `link` type, these embeds triggered the filter we had in place. This commit remedies that by using the existing URL regex pattern to list all the URLs contained in the message content and then checking if the embed url is a member of that list. If so, it's very likely that the embed was auto-generated from that URL, so we should ignore it. This approach deviates slightly from that outlined in #293. This does increase the probability of a false-negative, as a "true" user-generated rich embed could also have a url that's contained in the message body. However, I've checked most of the triggers we have had in the past and none of the legitimate triggers would have been a false-negative under the new rules. Therefore, I think it's very reasonable to adopt this strategy. In addition to the change in behavior of the rich embed filter, I have also kaizened the existing regex patterns by compiling them at load time. Since we check a lot of regex patterns for every message received by the bot, this should be beneficial for performance. | ||||
| 2019-09-24 | Add `continue` in the except block | Matteo Bertucci | -0/+1 | |
| 2019-09-24 | Create default django admin user. | scragly | -1/+3 | |
| 2019-09-24 | Fix random text mistake in Dockerfile. | scragly | -1/+1 | |
| 2019-09-24 | Add docker build condition for CI. | scragly | -0/+1 | |
| 2019-09-24 | Remove unneeded Pipfile scripts and azure stages/vars. | scragly | -51/+14 | |
 |
index : bot | |
| A mirrored copy of the python-discord/bot repository. |
| aboutsummaryrefslogtreecommitdiffstats |