Mozilla has introduced updated guidelines for submitting extensions to the AMO directory (addons.mozilla.org), which will take effect on August 4. The most significant change is the removal of the prohibition on restricting access to extensions—extension authors can now limit access to the extensions listed on AMO at their discretion. For example, extensions can be made available only for internal use or for closed user groups.
Other changes:
- The terminology regarding the collection and external transmission of data obtained from users or related to their activities has been changed. The overall principle remains the same—extensions are allowed to transmit only data directly related to the functionalities performed and with the user's explicit consent. The term "data collection" was interpreted by some developers as a separate category, distinct from data transmission and associated with information accumulation, whereas in both cases, it implied only the transmission of data outside the browser. In the new rules, all references to data collection have been replaced with "data transmission."
- Extension authors are allowed to place privacy policy rules externally servers, and not only within the AMO directory itself.
- Rules regarding the use of the userScripts API have been added, which can now only be used in extensions with script managers designed specifically for injecting handler scripts into pages, and it is prohibited to use it for altering the behavior of the script manager itself.
- Requirements for providing the source code of the extension, suitable for review (without obfuscation or minification), have been expanded. The code of dependencies used in extensions must now be included in the source package, or similar dependencies must be loaded during the build through official package managers.
Source: opennet.ru
