Installation
The custom browser add-ons four main components for Self-Sovereign Individual - window.ssi
(global API), browser.ssi
(WebExtensions API), services.ssi
(SSI Store Service) and about:selfsovereignindividual
(Setting Page) - in the Firefox.
Also, those components can easily add-on to other firefox forks as well, so you can choose another implementation. And your implementation, too!
Please choose the best for you.
System Requirements
https://www.mozilla.org/en-US/firefox/128.5.0/system-requirements/
Install from source
- Set up your editor - https://firefox-source-docs.mozilla.org/contributing/editor.html
- Check out from https://gitlab.com/studioteatwo/gecko-dev-for-ssi
git clone git@gitlab.com:studioteatwo/gecko-dev-for-ssi.git --depth 1
- Build
cd gecko-dev-for-ssi
./mach build
- After that, you can choose
./mach run
(for interactive) or./mach package
(for static).
Install from the binaries
Download the one for your platform from the distribution sites.
License is MPL-2.0. These builds are distributed for purpose of reserch and proposal to Firefox and the World Wide Web.
Tip
Tip
To verify the installer file (and the build process), please use attached “verification.txt.asc”. The signed public key is included in PGP message.
Tip
Tip
Currently these builds are pre-release-style release. Please hold the ctl key and right-click on Mac and Windows.
GitHub Releases
https://github.com/Browser-for-SSI/gecko-dev-pkg-distributor/releases
The build script relies heavily on the Floorp projects. Thanks to the Floorp community!
Install other firefox forks
Tor Browser version
- Set up your editor - https://firefox-source-docs.mozilla.org/contributing/editor.html
- Check out from https://gitlab.com/studioteatwo/gecko-dev-for-ssi
git clone git@gitlab.com:studioteatwo/gecko-dev-for-ssi.git --depth 1
git checkout mvp-tor
Configure
Depending on your build, you may need to configure manually in about:config
.
requirement | key | value |
---|---|---|
MUST | security.nocertdb | false |
Versioning
These builds are forked and therefore managed by versioning both the custom add-on browser and the base browser. The version is difined below:
v<custom-browser-version><custom-browser-branch>-<base-browser-version><base-browser-suffix>
For example v0.0.1mvp-128.5.0esr
is destined for a 0.0.1 release from mvp branch, based on the Mozilla Firefox 128.5.0 ESR release. If v0.0.1beta-14.0-1tor
, it means a 0.0.1 release from beta branch, based on the Tor browser 14.0-1 release.
And, to distinguish with the branding, the install path and so on of the base browser, the namespace ssb
is defined.