[baobun]

"Safety".

The thinking is that users are a danger to themselves and will be tricked by threat actors to add some CA cert to the trust store, paste commands into the js console, or download and sideload malicious extensions no matter what controls are in place so therefore these possibilities must be removed.

[jimjimwii]

Those same users will be tricked into downloading the "secure bowser" which has these tools. This is a nonsensical argument.

To this day, firefox is still the only browser that prevents its users from running custom extensions without Mozilla's blessing, likely motivated by the same garbage argument.

I have very little hope for Mozilla at this point and sincerely hope that they fail soon so that better open source browsers can take its place.

[The_SamminAter]

No, you can. In regular Firefox (without doing any shenanigans) the extension will be installed for the session (until the browser is closed), but Firefox Developer Edition lets you just install and run unsigned/invalid extensions (which is very useful if you occasionally have to change your clock back to 2018 and don’t want to lose all extensions).