Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Caution icon on Plugin cards to suit with new Guidelines #1391

Open
CJStyles123 opened this issue Sep 5, 2022 · 2 comments
Open

Comments

@CJStyles123
Copy link

CJStyles123 commented Sep 5, 2022

Is your feature request related to a problem? Please describe.
my feature request is a bit realted to a problem which can cause account risk, which is why this feature will help.

Describe the feature you'd like
There should be a Caution Icon on Plugin Cards if the specified Plugin isn't on the BetterDiscord Website/Plugin Repo...
Some Plugins can cause Account risk or breakage to the guidelines of BetterDiscord. This can help and be less of a hassle of finding Plugins which aren't allowed and deleting them remotely quick.

  • When the Icon is hovered, a Tooltip showcases that this hasn't been found on the BetterDiscord website and could potentially put the Account in risk of any API spam/other ways of getting banned.

Additional context

  1. Plugin has a Caution icon on it, when hovered prompts a Tooltip indicating that this Plugin is not on the BetterDiscord Plugins list to ensure the safety of the Users using it.
  2. Users will then have knowledge that they shouldn't have it and delete it so they're not in potential risk in the future.
@Tropix126
Copy link
Member

This has been proposed before, but would require a few things before/if it happens.

  • BD would need a way to match an installed plugin to a plugin on the site. There are three ways to do this, which is by checksum, by filename and by just name in general. The only reliable way to do this is by checksum, which would require a dedicated endpoint on the site.
  • This couldn't apply to themes, since themes are often modified by the user, changing the checksum. Only way around this is a standard for configuring themes without modifying file contents (which has been planned on, but likely isn't coming especially soon).
  • This should probably come after BD has a standard updater for official plugins on the site, since that's the main security concern at the moment.

@TheKodeToad
Copy link

TheKodeToad commented May 27, 2023

I don't think there's really a risk with themes, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

4 participants