Firefox Add-On Distribution Agreement
(a) relationship with Mozilla. You will provide Mozilla with accurate information and updates when registering and all communications with Mozilla, in conjunction with your add-ons. The descriptions and other data you provide via the add-on are in good conscience. If you and Mozilla don`t have a written agreement that says something else, your add-on does not in any way mean that it is produced, sponsored or supported by Mozilla. “To respect the privacy of our add-on developers, we prefer not to share statistics on the number of veiled add-ons. (a) the remoteness of the distribution by you. You can stop distributing your add-ons at any time by removing your AMO add-on. You agree that setting the maintenance or distribution of add-ons does not necessarily remove your add-on from end-user computers, hardware or other devices, or from a part of AMO in which previously downloaded applications are stored on behalf of end-users (if any). Signed add-ons are automatically distributed by Mozilla on AMO. Links to unsigned add-ons are available for distribution.
(e) change. Mozilla can update this agreement regularly. The update of the agreement will be available online. If the changes are substantial, we will announce the update via Mozilla`s usual channels for ads such as blog posts, forums or emails. Your subsequent distribution of your add-on after the effective date of these changes is your consent to such changes. To make your assessment more convenient, we will publish a validity date on the agreement. We are responding to a special complaint that has called several Paywall bypass services. It wasn`t just about your add-on. “Firefox extensions, which contain veiled code, will be deactivated today (June 10) in accordance with an add-on policy updated by Mozilla. In the original May 2 announcement, Caitlin Neiman, community manager add-ons on Firefox, said: “We will continue to allow the code mined, chained or otherwise generated by the machine, as long as the source code is contained.
In 2017, Mozilla made significant changes to the Application Programming Interface (API) for Firefox extensions and replaced the long-standing XUL and XPCOM APIs with the WebExtensions API, which is imbued with the Chrome API.    Firefox extensions are now largely compatible with their Chrome counterparts.  At the same time, plug-ins have become obsolete, with the exception of Adobe Flash Player.  (apps created with Firefox`s UXP range, however retain the old add-on features.[ 8]) llant akka tura a`as n ttawilat iw snefli n (add-ons) izegrar-isemmaden Firefox,maca WebExtensions ad yuɣal d tagnut sya ɣer taggara 2017.tigrumma nni`en n ifucka,ernud (add-ons)izegrar-isemmaden n afelselfu, Add-ons bootstrap ed SDK add-on tettwara ɣeluy n uzal n sen deg yiwet n tagwnitt. Add-on is the Mozilla term for software modules that can be added to Firefox`s web browser and related applications. There are three types: extensions, designs and plug-ins.  Mozilla hosts them on its official add-on website.  Full agreement.
This agreement represents the entire legal agreement between you and Mozilla regarding the distribution of add-ons and completely replaces all other related agreements between you and Mozilla, unless you have a negotiated and signed agreement separately in conjunction with a specific add-on (“Custom Agreement”), in which case the Custom Agreement controls. The hypertext documents of this contract, including. B revision guidelines, are included as a reference. The Mozilla supplement site is the official repository for Firefox Add-ons.  Unlike mozdev.org which offers free accommodation for Mozilla-related projects, the add-ons site is user-friendly. By default, Firefox automatically checks for updates for installed add-ons.  The open source nature of Firefox and other Mozilla software allows you to download and edit the source code for free.
Comments are closed.