3 ms·
They could trivially bury full add-on market access under 5 scary models and a password or something, but instead they use an absurdly cumbersome mechanism.
by anonymousab 4y ago
They could trivially bury full add-on market access under 5 scary models and a password or something, but instead they use an absurdly cumbersome mechanism.
- Zak 4y agoIt seems like there should be four levels: Recommended extensions, those that are currently available are vetted by Mozilla staff, not only for safety, but for utility and alignment with Mozilla's goals. These require no warnings or disclaimers. Community approved extensions would be on AMO and approved by staff-selected community members for safety and policy compliance. No warnings, but a link/checkbox/toggle at the bottom of the extensions page. All of AMO - this should need a toggle to turn on, and a warning that extensions have not been tested and could be unstable or malicious with a second checkbox to acknowledge. Local install - this should be buried in the settings and called something like "I am an extension developer". Turning it on should pop up an additional warning about other peoples' code being dangerous. Actually installing an extension should require separate use of a file manager or command line, and then enabling it inside the Firefox UI. The current approach reminds me of Apple's app store, except it's much harder to get on the recommended list than to get an iOS app approved. All of which is why I use Kiwi Browser.