AI Context Menu is still displayed if browser.ml.chat.enabled is set to false:
https://bugzilla.mozilla.org/show_bug.cgi?id=1994785
"Ask an AI Chatbot" context menu is not hidden, even if Machie Learning is disabled:
https://bugzilla.mozilla.org/show_bug.cgi?id=1995119
Mozilla has pretty much ignored this issue for an entire month.
And then they constantly try to shove it into their products, with no way to disable it. I'm assuming the user data would show that quite a lot of people would turn it off, so to not ruin your own statistics for the next shareholder/investor meeting, you need to force them
You would be wrong — outside of the Hacker News bubble very few people mess with their default settings, in any app.
My about:config settings still disable the stuff. I get no AI Context Menu.
I believe these are all the settings I have disabled for AI:
browser.ml.chat.enabled
browser.ml.chat.menu
browser.ml.chat.page
browser.ml.chat.page.footerBadge
browser.ml.chat.page.menuBadge
browser.ml.chat.shortcuts
browser.ml.chat.sidebar
browser.ml.enable
browser.ml.linkPreview.enabled
browser.ml.pageAssist.enabled
browser.tabs.groups.smart.enabled
browser.tabs.groups.smart.userEnable
browser.tabs.groups.smart.userEnabled
extensions.ml.enabled
sidebar.notification.badge.aichat
Am I missing anything?
I do have these additional settings.
browser.ml.chat.maxLength=0 browser.ml.chat.prompt.prefix="{}" browser.ml.chat.prompts.0="{}" browser.ml.chat.prompts.1="{}" browser.ml.chat.prompts.3="{}" browser.ml.chat.prompts.4="{}" browser.ml.chat.shortcuts.custom=false browser.ml.linkPreview.longPress=false browser.ml.modelHubRootUrl="example.com"
Ah...you ask which ones need to be disabled? Find it yourself. You have the right to disable it.
> The Mozilla Manifesto: Principle 9
> Commercial involvement in the development of the internet brings many benefits; a balance between commercial profit and public benefit is critical.
If you don’t open that, I’d be surprised if anything was instantiated or sent at all.
Firefox also collects usage data if individual features (which can also be disabled), so they’ll learn about the adoption soon enough.
Unfortunately, "configuration" is the survey. I detest both configuration and surveys. Modify the open source code and rip out the Artificial Inference code because Firefox is open source, or build software from scratch: servo, ladybird, your own web browser based on a survey.
- My understanding is that OCSP stapling stops leaks, because the browser can get OCSP data from the server instead of needing to fetch it separately.
- Last I heard, Firefox was in the process of removing OCSP responder checks (precisely for privacy reasons) in favor of CRLite-based revocation checks—are you sure they didn’t remove whatever setting you’re referring to from the UI because it’s no longer relevant?