Updated Addon Policies (markdown)
parent
3843ff6df0
commit
ac53cbedb6
|
@ -1,20 +1,5 @@
|
|||
## General
|
||||
1. All addons must be in public GitHub repositories.
|
||||
2. All addons must not negatively affect users.
|
||||
3. All addons must not target specific users or groups.
|
||||
4. All addons must not collect user data without opt-in consent.
|
||||
# Documentation has moved to https://docs.betterdiscord.app/
|
||||
|
||||
## Themes
|
||||
1. Themes must only use `@import` with Google Fonts or GitHub. This does allow for GitHub-related CDNs as well as GitHub pages.
|
||||
2. Themes must not abuse GitHub's raw links for `@import` statements.
|
||||
## Plugins https://docs.betterdiscord.app/plugins/introduction/guidelines
|
||||
|
||||
## Plugins
|
||||
1. Plugins must not introduce new remote libraries.
|
||||
- Existing remote libraries can still be used, but are officially deprecated to be disallowed in the future.
|
||||
2. Plugins must not be obfuscated and/or deceitful.
|
||||
3. Plugins must not modify globals or existing prototypes.
|
||||
4. Plugins must not use BD globals outside of `BdApi`.
|
||||
5. Plugins must not attempt to modify the BD UI. This is partially for consistency and partially to decrease the number of render issues caused by plugins.
|
||||
6. Plugins and their corresponding libraries shall not operate outside of their intended functionality.
|
||||
- This includes but is not limited to swapping out components unrelated to the plugin, introducing additional buttons, badges or other unrelated elements.
|
||||
7. Plugins must not make use of or read user tokens, emails, or passwords.
|
||||
## Themes https://docs.betterdiscord.app/themes/introduction/guidelines
|
Loading…
Reference in New Issue