Raymond Hill (Gorhill), the developer of uBlock Origin, released the Firefox add-on uBlock Origin dev build to Mozilla's Firefox Add-ons website recently.
Active uBlock Origin Beta users on Firefox may wonder why the development build version was released as a new add-on and not on the beta channel of the primary uBlock Origin add-on listing.
Update: The extension is no longer available on AMO. It is now self-hosted and can be downloaded from the project's GitHub page.
From now on, the beta version will be signed and self-hosted here. If I did everything right, it should auto-update itself. You only need to click on the beta version file, uBlock0.webext.signed.xpi above. The stable version and the beta version auto-update independently of each other. If you still have 1.15.11b0, I believe you will have to manually install 1.15.11b1 from here for auto update to be enabled. Afterward, the beta version will auto-update itself when a new beta version become available.
The decision means that developers cannot publish release and beta versions of add-ons using a single add-on listing anymore. Developers who maintain development and release channels of their extensions for Firefox need to create multiple add-on listings now to continue that practice.
Existing beta version users of uBlock Origin will be moved to the latest release version of the extension automatically once the stable version reaches a version that is greater than that of the beta version.
As per email, those using the beta version of uBO will be automatically moved to the latest release version of uBO when the release version become greater than the last version available in the beta channel.
Firefox users who want to use the development build version of uBlock Origin need to install uBlock Origin Dev Build, a new add-on, to do so. This version works just like the old beta version but is maintained now on a separate channel.
Since the extension is not linked in any way to the stable version (or vice versa), all settings and subscriptions will be set to default upon installation. Users who want to retain the settings need to use the extension's settings backup and restore functionality to address the limitation.
Here is how that is done:
We don't know how many add-ons are affected by the change but it will change things around quite a bit: Mozilla AMO will list multiple versions of the add-on now instead of just one, users who run beta editions need to switch to development builds (if offered) to continue using these, and the separate listing of development add-ons may lead to the installation of these add-ons by users who wanted to install the stable version.
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats (video ads) or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.