Comment by kgwxd
1 day ago
The only correct move would be remove the option, remove all AI code, and move it into extensions. If the extension security policies, and other restrictions, don't allow all the things they want to put in, then GOOD, they don't go in.
I also think should be moved into extensions. However, extension security policies and other restrictions do not have to necessarily be so restrictive; there can be permissions but for extensions that you can install and uninstall by yourself it can be useful to be able to load native code .so files (since you might want to do things other than what the browser does by itself). This permission would not be made available to the official extensions, so that you can write it in C and then must compile them by yourself if you want them with native codes
Older Firefox extension feature-sets were quite powerful before Google financially coerced / induced them to support the kind of crippled version that is today's "Web Extensions". Many developers were angry enough to fork Firefox just to retain that feature ( https://www.palemoon.org/ ).