Live data from Hacker News

Firefox 42 will not allow unsigned extensions

wiki.mozilla.org

1–10 of 315 posts

Re: Firefox 42 will not allow unsigned extensions

#3

It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.

The other assumption being that there is a distinction between 'developers' and 'users'.

Re: Firefox 42 will not allow unsigned extensions

#4

It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.

Did they say why beta wouldn't have this setting? If anything beta is closer to release and developer would target that. Developer edition is still nightly if I'm not correct?

Re: Firefox 42 will not allow unsigned extensions

#5
post #4

It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.

Did they say why beta wouldn't have this setting? If anything beta is closer to release and developer would target that. Developer edition is still nightly if I'm not correct?

I don't see anything about why the beta, but I did see the following in the FAQ. Maybe this will help:

"There will also be special unbranded versions of Release and Beta that will have this setting, so that add-on developers can work on their add-ons without having to sign every build."

Re: Firefox 42 will not allow unsigned extensions

#7

It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.

The link also says that there will be builds of normal (release) and beta Firefox that do not have this limitation, for those that want them.

(In addition to people always being able to recompile the browser with whatever modifications they want, of course.)

Re: Firefox 42 will not allow unsigned extensions

#8
post #6

What is the point of this? Shouldn't users be allowed to make their own decisions no matter how stupid or dangerous?

Users still can, they can download one of the provided builds that do not have this restriction.

The issue is that most users don't understand software on a deep level, and just click "yes" on dialog boxes, etc.

It does make sense to keep the defaults where it prevents most users from harm.

Re: Firefox 42 will not allow unsigned extensions

#9
An important point is that the review process before signing takes seconds, according to the article. Considering the frequency of FF updates, it's an important point.

Now, let's just hope that the other side of the coin is a concern for API backward compatibility, so that people don't need nightly versions of addons and a developer edition to keep their addons in a usable state...

Post reply on HN