On Tue, Jul 15, 2008 at 5:59 PM, Eric H. Jung <[EMAIL PROTECTED]> wrote:
> From: Onno Ekker <[EMAIL PROTECTED]> > > >A better bet might be to become a trusted add-on. I don't think the > concept of trusted add-ons is any safe, but since amo uses it, it is > probably your best bet to prevent future > >update problems. Unfortunately there isn't too much info about trusted > add-ons either, but I can imagine becoming trusted involves a lot of hanging > around and begging on irc ;-) > > One of my add-ons is trusted. I neither begged nor even asked for it to be > trusted. Indeed, I didn't even know what a "trusted addon" was. One day, I > went to upload a new version of this addon to AMO and was presented with the > option to publish the new version to the sandbox or to the public. It'd > become trusted. I still don't really know how it happened :) > Now that is very strange... Why do they trust an add-on and not a user? They trust you to not put malware, remote java, memory leaks, etc in one add-on, but think you might put it in one of your other add-ons? Or do the other add-ons have co-authors they don't trust? And then you were lucky enough to see it in time, otherwise you might have got stuck with an extension in the sandbox, due to bug 432121 (filed by you :-)) Onno
_______________________________________________ Project_owners mailing list [email protected] https://www.mozdev.org/mailman/listinfo/project_owners
