arkenfox
`browser.ml.enable` as (commented-out) hint, as it captures a significant category of functionality
Hi, given discussion in #1998 I will keep it short: I think settings such as browser.ml.enable also provide benefit as hint/option to Arkenfox users simply by being listed for awareness. I think that's done with more settings. If current AI features are not a problem, one could choose to disable them in anticipation of future undesirables and/or unwanted excess bloat functionality.
Feel free to bluntly close if disagree. I merely want to point out a different flavor of benefit.
for reference - https://github.com/mozilla/policy-templates/issues/1230#issuecomment-3224257069 - let's see how moz policies separates into some sort of local model vs other
that said, for now, I see no privacy issues and feel this is just completely out of scope - the user chooses to use a chatbot or not, otherwise it's all local, AFAICT (but I haven't down any deep diving). Adding prefs means maintaining them and if active it just adds more hoops for users to jump through to get what they want
I do understand that OP says to just add the one main pref for the info factor, commented out
https://old.reddit.com/r/firefox/comments/1ow29g3/coming_soon_ai_window/nonersr/
We'll have an easy kill switch coming soon as well for the existing stuff
https://old.reddit.com/r/firefox/comments/1ow29g3/coming_soon_ai_window/nop1toi/
We're finishing up the requirements for the kill switch tomorrow, designing it up next week and then coding it the week after. It does need to be QA'd before release, which takes a little time to get to the release candidate but not too much time. It is coming sooner rather than later.
TBH, I'd rather wait for this master pref/UI to land and test if/what it removes, such as context menus etc
Both this point and your previous one are valid. I have no interest in forcing my request, as you clearly understand my intention.
-------- Original Message -------- On Friday, 11/14/25 at 08:12 Thorin-Oakenpants @.***> wrote:
Thorin-Oakenpants left a comment (arkenfox/user.js#2004)
https://old.reddit.com/r/firefox/comments/1ow29g3/coming_soon_ai_window/nonersr/
We'll have an easy kill switch coming soon as well for the existing stuff
https://old.reddit.com/r/firefox/comments/1ow29g3/coming_soon_ai_window/nop1toi/
We're finishing up the requirements for the kill switch tomorrow, designing it up next week and then coding it the week after. It does need to be QA'd before release, which takes a little time to get to the release candidate but not too much time. It is coming sooner rather than later.
TBH, I'd rather wait for this master pref/UI to land and test if/what it removes, such as context menus etc
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
https://old.reddit.com/r/firefox/comments/1ow29g3/coming_soon_ai_window/nonersr/
We'll have an easy kill switch coming soon as well for the existing stuff
https://old.reddit.com/r/firefox/comments/1ow29g3/coming_soon_ai_window/nop1toi/
We're finishing up the requirements for the kill switch tomorrow, designing it up next week and then coding it the week after. It does need to be QA'd before release, which takes a little time to get to the release candidate but not too much time. It is coming sooner rather than later.
TBH, I'd rather wait for this master pref/UI to land and test if/what it removes, such as context menus etc
Regarding this, it seems like a UI toggle killswitch for this was added for enterprise administrators, but I can't find any info about this being something they're planning to add to consumer firefox, has there been any word on that since?
