@raymaccarthy @firefoxwebdevs You have never needed to use about:config. You can still quite happily browse the web using Firefox without going into about:config.

@firefoxwebdevs what's about mozconfig.cfg build option?

@firefoxwebdevs
Awesome! It seems like the controls are able to be customized.

Its great that Firefox is listening to users. Though the blog seems to have an error on my end, its possible its only on my machine. Its possible that some link is broken

@ArneBab @firefoxwebdevs

some people really like those other features though. Translation is one of our most requested features ever, and we couldn't implement prior to local AI. We weren't going to ship your web pages to some web service so they could see what you browse. But to other folks "AI is AI" and they want it off.

Feedback in Nightly is how we figure out if there are too many options or not enough.

@firefoxwebdevs the tiny minority of people who choose to use firefox at all dont want AI. it should be off by default if its being shoehorned in anyway, but since mozilla doesnt care the least they could do is not neuter the name.

"kill switch" bites, "AI controls" licks

EDIT: misread formally as formerly, still dont like this

@miller @mkj @firefoxwebdevs easy way would be to use https://addons.mozilla.org/en-US/firefox/addon/enterprise-policy-generator from https://mastodon.social/@s_hentzschel@agenedia.com

@firefoxwebdevs Do you know if there will be a popup to let users know when it launches? (Like a product tour "what's new" type of thing?)

@firefoxwebdevs boooo. AI shouldnt even be in the browser. Thats what the people told you.

@madduci @firefoxwebdevs afaik the default is already opt in in a way - for example, the link summary feature asks you if you want to enable summarisation before actually doing anything.

the point of the block is a browser wide, 'don't even ask' toggle

@plwt @firefoxwebdevs
The word "happily" is out of context.

I have used Chrome (Android/ChromeOS)_, Edge (windows), IE (various cursed versions on Windows) and Safari (Apple Things) to "browse the web" and get a different browser such as Firefox, seamonkey, Vivaldi, Waterfox, Chromium and others.

I'd be on Vivaldi if about:config didn't exist. The only reason I'm not is more flexible script blocking on Firefox to suit TheGuardian web news.

NOBODY ASKED FOR THIS AI BULLSHIT!!!

you’re traitors to the open web cause. this should have been an extension, not a complete integration in the browser.

@firefoxwebdevs

@dveditz yes -- so why a wording that feels so massively manipulative?

For example I don’t mind image description. I don’t even mind my mastodon ALT text being mined to describe images (such a feature actually helps blind people).

But when I click "block", I mean "block" and not "Ask me whether I really want to disable all these cool features and then again whether I want to enable some selected features despite the block".

@firefoxwebdevs

@ArneBab but it doesn't enable future feature by default.

You're blocking the entry points to these features, so they cannot be enabled.

@raymaccarthy @firefoxwebdevs Keen to understand more - why do you need to block scripts to be able to view the Guardian website?

What happens when you try to view the page without this?

Is there any error message?

#fxhelp

@raymaccarthy @plwt fwiw Vivaldi does have AI features like translation, and it even sends text to the cloud to perform that translation.

@firefoxwebdevs

Immediately restore the work of japanese language translators that you paved over with AI slop

AI Controversy Forces End of Mozilla’s Japanese SUMO Community

The SUMO Japanese team quits en masse, accusing Mozilla’s AI system of erasing years of community translation work.

Linuxiac (linuxiac.com)

#Firefox #Mozilla #Japanese #GenAI #AISlop #LLM

@tay @madduci correct! You're blocking the entry points for these features, and features like it in future.

@firefoxwebdevs enable future feature by default happens by default.

If that gets disabled on clicking [disable all] (or such), that’s the same choice, but without feeling as manipulative.

And "blocking the entry points … so they cannot be enabled" followed by options to enable them individually is part of what feels so wrong.

@mausmalone I don't think so. But of course it will be mentioned in release notes. We're not exactly being quiet about it.

@ArneBab We're stumbling on the wording here. 'Enabled' to many people means the feature is active. That's why we went with 'available' for features that aren't actively running, but their entry points are available.