Replies: 1 comment 1 reply
-
|
Setting up multiple profiles can be a real hassle because you have to configure everything the same way for each one. With a configuration file like this, users could make things much easier. They’d still be able to install or remove extensions directly in the browser without touching the config file. The only downside is that those changes wouldn’t sync and persist across profiles, but the advantage of keeping it in that way is that users will be able to install, try and uninstall extensions if desired. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As long as I know, most of the Chromium-based browsers has a mechanism to specify extensions that should be installed on the browser.
So I think that a part of your users(mostly those who have dot config files or uses Nix) will benefit from this proposal.
They could have some config options to declaratively and reproducibly communicate to the browser about some things that need to be installed or uninstalled across all the browser profiles, that's the behavior in Chromium(at least in Brave and Vivaldi).
From Linux user that does not uses Nix they could have a dot file like this:
And those zen mods and firefox addons will be automatically managed by the browser.
From a Nix-user perspective, this could allow me to declare my configuration like in the following snippet:
BTW I'm currently maintaining this flake that distributes the browser in Nix-compatible systems.
I would love to have this available. By the time I write this... happy new year's evening! :)
Beta Was this translation helpful? Give feedback.
All reactions