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 Request] #625

Open
BotterManTingGoes opened this issue Apr 13, 2022 · 1 comment
Open

[Feature Request] #625

BotterManTingGoes opened this issue Apr 13, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@BotterManTingGoes
Copy link

BotterManTingGoes commented Apr 13, 2022

Describe the feature request
In the new update to check harmful plugins, include a reason or a context menu as to why the plugin was blocked not just a "x is harmful to your pc" so the end user has better knowledge on whether they want to accept this risk.

What Plugin would it be for?
Powercord

Expected behaviour
A button next to the "Load them anyways (dangerous)" button that would say something like "Extend/Advanced" Which will tell you why each plugin was blocked i.e one could be blocked for being a token logger, another one could be blocked due to known memory leaks in that plugin. What i'm getting at is there isn't any information on how these "dangerous" plugins are added to the hash list or what would be enough to consider/or make them dangerous enough to add to the known harmful check/hash list.

EDIT: sorry forgot to change title, yikes.

@BotterManTingGoes BotterManTingGoes added the enhancement New feature or request label Apr 13, 2022
@nea89o
Copy link

nea89o commented Apr 14, 2022

I don't think cynthia intends to add this. She has had a history of banning creators from the powercord community and has continuously done so without specifying any reasons. The justification of these current ban lists are that there might be added malicious code in revenge to getting banned. However, this hasn't happened so far, at least not my knowledge. Be aware that blocked plugins, even if you enable them don't get auto updated. If you want to disable this anti-feature at once, see my comment under the relevant commit.

Edit: Malicious code in plugins has happened before, when none of these things were in place, but it hasn't even been attempted since these measures have been in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants