Firefox doesn't allow permanent unsigned extensions for security reasons. Thus, we should either publish the extension to the Firefox (and Chrome) marketplaces OR sign the extension locally. The former is probably the easiest route for users long-term. For the latter, I found this guide which I tested and can confirm is working: https://linuxconfig.org/how-to-create-package-and-sign-a-firefox-web-extension. In a nutshell you create an account at Mozilla's developer hub to get the API keys required for signing, publish the extension as an unlisted private extension, wait for automated approval and finally get a signed XPI file in return. Then, you can just load that file at about:addons > gear icon > Install add-on from file. This makes it a permanent install.
Firefox doesn't allow permanent unsigned extensions for security reasons. Thus, we should either publish the extension to the Firefox (and Chrome) marketplaces OR sign the extension locally. The former is probably the easiest route for users long-term. For the latter, I found this guide which I tested and can confirm is working: https://linuxconfig.org/how-to-create-package-and-sign-a-firefox-web-extension. In a nutshell you create an account at Mozilla's developer hub to get the API keys required for signing, publish the extension as an unlisted private extension, wait for automated approval and finally get a signed XPI file in return. Then, you can just load that file at
about:addons
> gear icon > Install add-on from file. This makes it a permanent install.To be discussed.