![]() If you get stuck in the queue, you can email me directly (my username at ) and I'll do my damnedest to get things moving again. I believe AMO hired (or is hiring) another dedicated staff member to help out with review times. If Mozilla takes too long in verifying an extension (something very common with certain quickly updated extensions, that sometimes take months to be certified by Mozilla), does that mean that the developer can only cross arms and wait for approval? It will take us a long time to get something ready for release, but I want to acknowledge that we're not blind to the issues with the current system. within Mozilla, and people are actively working on figuring out a permissions-based, unified add-on API for all of our platforms (including Firefox on Android and Firefox OS). There is significant frustration at the state of add-on APIs, review times, etc. For developers, you can of course use an unbranded, DevEdition, or Nightly build of Firefox and disable the signature requirements, should you want to install unsigned add-ons yourself. It sucks, but we don't have any better options at the moment. ![]() The chain of trust has to be compiled into the release binaries if we want to create a sufficiently high bar for malicious / side-loaded add-ons.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |