Re:Firefox 42 will not allow unsigned extensions
by Animats on Tuesday August 11, 2015 @01:16AM
(#10039213)
That's for non-public add-ons. If you submit a public add-on, even a minor update, it has to go through the AMO bureaucracy. I currently have an update that was uploaded on July 10, 2015, and is at queue position of 64 of 137. There are no code changes; it's just being updated because Mozilla changed their build system.
This seems to be part of Mozilla's effort to be more like the Apple and Google stores.
Mozila AMO - Learn to embrace the pain.
Re:Firefox 42 will not allow unsigned extensions
by kpcyrd on Tuesday August 11, 2015 @05:49AM
(#10039920)
Actually, it's their effort to prevent AMO from ending up as malware riddled as the Chrome Store.
Addons are running in the chrome context and are thus pretty powerful. It's trival to compromise the whole computer if they aren't reviewed.
Re:Firefox 42 will not allow unsigned extensions
by piyush_soni on Tuesday August 11, 2015 @12:23PM
(#10042274)
I wouldn't think Chrome Web store is full of Malware. Yes, it's not free of those, but the bad ones are quickly removed by both Chrome's policing, and users' flagging. That's how Mozilla should go forward. The problem with manual reviewing is, it depends on the 'volunteers' time availability, and a stupid Review system which is NOT FCFS. You are told you are 37th out of 150 in the queue, but you see that you either remain at that position while others are being approved, your queue position goes both up and down, and some times your add-on is instantly approved even when you are 100th in the queue. All this takes many days even if your users are waiting for a critical fix. This is the biggest turn off in uploading add-ons for Firefox.
Re:Firefox 42 will not allow unsigned extensions
by imakesnowflakes on Tuesday August 11, 2015 @04:17AM
(#10039667)
I have one uploaded on Mar 12, 2015, it is at position 25 right now. And it has been at around that position for quite a while.
Re:Firefox 42 will not allow unsigned extensions
by soapdog on Tuesday August 11, 2015 @10:31AM
(#10041297)
You can sign the addons and distribute it on other channels. If you want to have it on AMO then it takes a while to review. The process is done by volunteers
Re:Firefox 42 will not allow unsigned extensions
by e1ven on Tuesday August 11, 2015 @10:51AM
(#10041461)
This is one of the things which is frustrating about Mozilla.
I love that they stand for open protocols, free software and user privacy, but I don't love what they prioritize.
Reviewing extensions is critical to their user-experience. If this really doesn't have an team of paid staffers, that's unfortunate.
Re:Firefox 42 will not allow unsigned extensions
by soapdog on Tuesday August 11, 2015 @03:15PM
(#10043618)
It has paid staff and volunteers. More volunteers than paid staff IIRC. Reviewing stuff correctly takes time :-( sorry.
This can be mitigated by having more volunteers (or paid staff (or both)) to help though.
Re:Firefox 42 will not allow unsigned extensions
by tomjen3 on Tuesday August 11, 2015 @12:47AM
(#10039139)
If it passes.
Nobody knows what it checks for or how it works.
Re:Firefox 42 will not allow unsigned extensions
by icebraining on Tuesday August 11, 2015 @06:15AM
(#10040009)
Actually, the link says
> Files submitted for signing will go through an automated review process. If they pass this review, they are automatically signed and sent back to the developer. This process should normally take seconds
You may be thinking of a different type of review process, the signing one sounds almost instantaneous.