-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* feat: version 3.24 * chore: run updated black over the codebase * chore: add profiling files * chore: downgrade message editing failure to debug instead of warning * chore: bump logoo to 1.4.0 to reduce log upload failures * chore: move suggestions security violations to a higher handler for more metadata in logs * chore: bump logoo version * feat: add german translations * fix: blocklist remove without args Closes BT-38 * Update pt_BR.json (#83) * chore: move stats.py to logoo * feat: add SECURITY.md * fix: missing info in ConfiguredChannelNoLongerExists error Closes BT-42 * chore: remove overkill data * feat: add the notes command Also fix a whole bunch of other stuff * fix: tests * feat: make thread pings configurable at the user level BT-41 * feat: finish guild configs and localizing BT-41 * fix: localization Closes #73 * chore: remove a test we no longer needed * add todo * feat: allow resolving queued suggestions with notes BT-22 * fix: errors not propagating in some situations BT-49 * feat: log on missing base translation * fix: missing base translations * pt-BR localization updates and fixes for version 3.24 (#87) * Update pt_BR.json to version 3.24 * Clarify the pt-BR translation * Update en_GB.json --------- Co-authored-by: Davi <[email protected]>
- Loading branch information
1 parent
60aa4f0
commit 1f9cbad
Showing
31 changed files
with
1,004 additions
and
199 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
The latest master branch is actively maintained and any security patches will be applied to that branch. | ||
|
||
Older versions will not have patches back ported. | ||
|
||
## Reporting a Vulnerability | ||
|
||
### TLDR | ||
|
||
We recommend opening a security advisory on GitHub, as per the [documentation](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability). | ||
|
||
Alternatively, reach out to the maintainers via discord (`@skelmis`). | ||
|
||
--- | ||
|
||
### Your research | ||
|
||
We ask that anyone conducting testing: | ||
- Makes every effort to avoid impacting other users of our systems | ||
- Avoids any activities that disrupt, degrade or interrupt our services or may compromise other user data. This includes things such as spam, brute forcing, DoS, etc | ||
- Keeps vulnerability information private until we have had the ability to roll out fixes | ||
|
||
|
||
### Our commitment | ||
|
||
If you meet the expectations laid out, we commit to: | ||
- Acknowledge any reports and keeping you informed of how we are tracking on fixes | ||
- Acting in good faith when interacting with you | ||
- Recognising your contribution via means such as security advisories on the affected services and/or CVE's | ||
|
||
|
||
We will aim to fix any issues ASAP, however as we are not a dedicated resource this may not always be possible. As such, we aim for full resolution to all acknowledged issues within a 90-day period. If this is not possible, we will enter discussions with you as to the reason for delays. | ||
|
||
|
||
### Report details | ||
|
||
At a minimum, your report should contain: | ||
- The affected service | ||
- A description of the vulnerability | ||
- Complete reproduction steps | ||
|
||
You may include other items to your report as you please. Some examples may be: | ||
- The perceived impact | ||
- The perceived likelihood of exploitation | ||
- A list of users to credit for the disclosure |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.