After some controversy and confusion in regards to uBlocks future, Raymond Hill's uBlock Origin extension is now officially available for the Firefox web browser.
The past weeks have been filled with uncertainty about uBlock's future. It all started when Raymond Hill, better known as Gorhill on GitHub, announced that he would hand over development to another member of the development team.
It was unclear at first what this meant and why Raymond made that decision but he shed some light on the issue later on when he noticed that more and more of his time was spend on support related tasks and there especially on a never ending stream of requests.
He did create a feature-complete version of uBlock and settled for the name uBlock Origin for it after his extension was taken down by Google on the Chrome Web Store for a brief period of time.
That was not the end of it though. Today, this post was published on GitHub looking back at the transfer of ownership.
The conclusion is what is most interesting though as Raymond states that he will continue uBlock Origin development.
Even better, uBlock Origin landed on Mozilla AMO where it can be downloaded by all users of the Firefox web browser (it was previously only available for Chrome).
The add-on has not been reviewed by Mozilla yet which means that it is only available to users who have the direct link to its add-on page.
Once it is reviewed by Mozilla, it will become available to all users on the site meaning that it can be found in categories and searches from that moment on.
Even though uBlock Origin is technically a fork of the original uBlock, it has the support of the original author of the extension which sets it part from uBlock.
Considering that features were removed from the original uBlock by the new owner of the project, it is without doubt the better choice going forward regardless of whether you are using Firefox or Google Chrome.
Please note that you can download the latest version of the Firefox add-on as well as the latest dev version of said add-on from GitHub as well.
Generally speaking, it is not suggested to run dev builds of the add-on unless you help with the development of the add-on, for instance by testing the newest versions and reporting bugs back to the project.