-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add a plugin store #4
Comments
I'm unsure how much we can realize this because it conflicts with decentralization. At least the default source needs to be environment configurable in source. |
You can just have list of repos to gather infos from, with the last in the list being the most preffered source, no? |
No, because then we still have a central opinionated list, regardless of ordering that conflicts with decentralization. |
You can be decentralised and still offer defaults, make the sources customizable and ship with our default source, users can add or delete sources as they choose This behavior can also be found in ReVanced's upcoming update to their manager |
This is correct. The default can be configured via an env variable during publication. The source remains independent of any specific default. |
You should also add a way to change the signing key required for plugins to be verified as "trusted" |
If you're using the revenge distribution of the source code, the environment will configure revenge to be trusted as part of you already trusting this distro. Changing the key doesn't make sense, however you can trust other developers keys anyway in the first place, but you can't not trust revenge if you're using revenge as the distro. If you don't want to trust revenge, dont use revenge as the distribution and compile the source with your env or someone else |
You could still add the option to not trust it, and / or put your own signing key to replace Revenge's (for the like two people who are extremely privacy focused but are too lazy to recompile) |
This is illogical. If you run a distribution by Revenge you automatically trust it already. Not trusting the signature implies not trusting the distro as the signatory is the same. "Too lazy" and "extremely privacy focused" is mutually exclusive. |
There was a plugin called Plugin Browser for bunny, but that wasn't a built-in behavior. I'd like to see a built in plugin store in the client.
The text was updated successfully, but these errors were encountered: