Comment by zzo38computer
8 hours ago
I agree with you.
The extensions and plugins should be separated from the rest of the program, like any other extensions, and can be configured and disabled by the end user.
Some of the extensions might come with the distribution, but if so, there should also be another package available which is the same program but without any of the extensions included with it (and should be just as easy to find and use, rather than making it difficult), and also the possibility that if you downloaded it with the extensions it can be disabled, and that if you downloaded it without the extensions then you can still install them like any other extension if wanted.
People who do want the AI features can have them, but not as a core part of the browser (the extension mechanism can be enhanced if it is found to be insufficient, which would help with many other things as well; however, the end users should still be able to control the security features of extensions regardless of who wrote them or where they come from), and possible to get it without those and other potentially unwanted extensions.
Even many official features of WWW may be potentially unwanted; in some cases, these might be made as extensions, and in some cases, they might be made as options which can be configured and disabled. Either way, they should be documented; it is good to have good documentation for any software (and should not require an internet connection to use, even for a web browser).
No comments yet
Contribute on Hacker News ↗