As some may have already gathered from other discussion and the recent announcement I made for 2022 regarding Pale Moon, I am stopping the development of Basilisk.
The reasons for this are multiple:
- Basilisk was, first and foremost, released as development software to facilitate development of the (then in its early stages) platform code we build our applications on. Since the platform code has matured significantly, this reason for Basilisk has dropped away.
- Basilisk was also released to provide a differently configured browser than Pale Moon with additional features enabled that by design would not be included in Pale Moon (particularly support for DRM-locked media and WebRTC). Since DRM as well as WebRTC has not been functional for a while(1) and it seems it will never become functional in the future with the information available to me now, this also reduces the value of Basilisk as a second browser.
- Next, Basilisk provides a Firefox replacement for running unmodified Firefox "legacy" extensions. Considering Pale Moon will, with the next milestone, have that same functionality, there won't be a reason for Basilisk to provide duplicate extension running capabilities. While there is still a small potential benefit of using an Australis-based front-end for those extensions that might not have 100% compatibility with Pale Moon's GUI out of the box, it isn't sufficient by itself to justify the overhead for me personally to build, update and publish Basilisk.
A genuinely interested developer who wants to "take over the torch" from me regarding Basilisk who wishes to continue the browser's existence in terms of long-term maintenance and publication can contact me to take over the browser. That includes everything: the branding, rights to the logo and trademark, the domain, website, but also browser development and maintenance, and support for users. You will have to be fully self-sufficient in your administration and releases of the browser, and in keeping up with platform development. If necessary I can keep this board hosted here as a support channel in the initial stages, but whomever becomes the new application owner will have to moderate and be responsible. In consultation with me it may also be possible to continue to use our add-on infrastructure for a while but it is the idea that anyone taking over will basically do what I've done and not lean on any other project's resources (at least not without compensation of some sort).
If you fit the bill and are genuinely interested in carrying Basilisk forward, PM me. This is not first come, first served if there are multiple candidates -- I'll select the one I think is the best match.
(1) DRM/EME can't be used because Google refuses to license content decryption modules to us for use, and WebRTC because the implementation on websites that actually use this API only works with specific browser implementations of WebRTC even though we do pass Google's own WebRTC tests...