AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs nice
I think if it runs locally, AI features are quite useful. E.g. I use translations daily. Tab grouping and image alt texts would also be great. Unfortunately they are probably not eligible to run locally.
-
@fabio @firefoxwebdevs survey only shows a tiny fraction of the total userbase. why it should influencethe default?
@wojtek Interesting that you have a Vivaldi.net account, a browser that famously doesn’t include any AI features. Your question is a bit strange in this context, or maybe it’s just a bad attempt at being a contrarian.
-
@firefoxwebdevs @tay @madduci that feels more like "hide" than "block" to me
-
@duke_of_germany @firefoxwebdevs whereas the poll I actually ran, which shows how target users of the feature view translation, was practically useful.
@jaffathecake @duke_of_germany @firefoxwebdevs .. thank you Jake for at least trying to do SOMETHING constructive here despite Moz leadership’s stance on AI. I can live with a BLOCK AI button if BLOCKED is default (although I’d personally prefer your limited resources were spent elsewhere).
Given you (accurately) mentioned Mastodon is skewed against AI, I’m curious what non-Mastodon data does Moz have on actual interest for AI in Mozilla? (Beyond “everyone is doing it”.)
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs “Block AI Enhancements” should be checked by default, ya ding dongs.
-
@raymaccarthy @firefoxwebdevs It would need to cater for not only Windows and macOS (possibly multiple versions of both) as well as quite a few different Linux desktops. At the same time, it would need to have light and dark modes for all.
With Fx having the same broad style across most platforms feels much better to support and easier for contributors to work on.
@plwt @firefoxwebdevs
Only if your SW is broken and simply getting a window, then drawing its own controls. Perhaps years ago Firefox was changed to use its own renderer and CSS instead of system API calls for all controls etc.
I can even do a custom theme on Mint+ Mate, Win98, XP, Win7 and well written programs look native.How can you even know the Look & Feel? The entire concept of Firefox GUI must now broken.
That would explain the garbage scrollbars.
-
@raymaccarthy @firefoxwebdevs It would need to cater for not only Windows and macOS (possibly multiple versions of both) as well as quite a few different Linux desktops. At the same time, it would need to have light and dark modes for all.
With Fx having the same broad style across most platforms feels much better to support and easier for contributors to work on.
@plwt @firefoxwebdevs
Short answer, if you think that you are completely wrong about how a program should do a gui. You are writing about something with a custom skin, not a well behaved program. Even a QT based program can follow an arbitrary OS look and feel. Java can. So instead of creating and styling a funky scrollbar you FW tells OS: Scrollbar here this orientation & length.Winamp was 1st I encountered ignoring OS.
-
@raymaccarthy about:config isn't intended to be for user settings. That's why we've created a dedicated AI controls page, and we're the first to do so.
@firefoxwebdevs you should've have needed to be the first, you should never have added things users don't want. Make it plugins, then users can choose to add disgusting "AI" "features". @raymaccarthy
-
@firefoxwebdevs "AI is changing the web, and people want very different things from it. We’ve heard from many who want nothing to do with AI. We’ve also heard from others who want AI tools that are genuinely useful."
Have you? Because I've literally only heard the former. See e.g. virtually every one of the 966 comments on https://connect.mozilla.org/t5/discussions/building-ai-the-firefox-way-shaping-what-s-next-together/td-p/109922
@mike @firefoxwebdevs Preference falsification, it's seen as socially condemnable to be ok with AI, especially in the circles that Mozilla frequents, so I'm not surprised public comments trend negative. Given they've sent an anonymous survey out, I'm pretty sure the balance is split between the no-AI and AI everything camps.
I don't get the vitriol towards Mozilla, at least not for this change, they literally show you how to turn off their AI features
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs
It must be really uncomfortable for you and your team to see this outpouring of opposition to the direction you are being lead.I hope you know its not personal. But you must understand that it is deadly serious.
Please, hear us as we all shout in unison: STOP WASTING MONEY AND ENERGY ON GRIFTS AND JUST MAKE THE BEST DAMN BROWSER YOU CAN MAKE.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs If you physically and permanently remove all AI-related code from Firefox, I might start using it again. Not until.
-
@duke_of_germany @firefoxwebdevs they're aware of the sentiment. I'm sure you're aware that Mastodon has a high representation of folks who don't like AI, so presenting evidence that Mastodon users don't like AI is kinda… well… not really useful.
@jaffathecake @duke_of_germany @firefoxwebdevs i keep seeing this cop-out, but i have yet to see any polling from mozilla that says a majority of their users do want AI in their browser.
e.g. 14 days ago i see an informal poll in reddit with the same conclusion - https://www.reddit.com/r/firefox/comments/1qhfvkw/interested_in_your_views_on_ai_in_firefox/
the thread inviting people to comment on the AI window a few weeks ago was the same thing, overwhelmingly negative - https://connect.mozilla.org/t5/discussions/building-ai-the-firefox-way-shaping-what-s-next-together/td-p/109922
so if in community after community people are nearly unanimous about the pivot to AI, it seems like the burden is on firefox dev team to show that there is some silent majority that is loving it rather than insisting that every community is an echo chamber
-
@ArneBab @firefoxwebdevs
I have no idea. I hadn't seen this UI even internally until a few days ago. -
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs please make separate version without any AI, without translate (made by monolinguals) and call it betterfox. It will have succes! Also less code - less bugs, less mistakes and less vulnerabilities.
Less work - more output!
-
Google is not pushing Mozilla to use AI features. To the extent people get their answers from AI rather than doing a Google search that is _costing_ us money.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs it should be disabled by default. Also telemetry and ads tracking kill switch when?
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs@mastodon.social Maybe it would've been better to just not call the on device features AI features at all. People would be more willing to try them if they don't associate them with massive GPU farms.
-
@ArneBab @vex @firefoxwebdevs @dveditz
Dont want "AI" in my Browser is the first and only thing there is to say about this.
We all know the implications of this technology anyway, right?
-
@firefoxwebdevs nice
I think if it runs locally, AI features are quite useful. E.g. I use translations daily. Tab grouping and image alt texts would also be great. Unfortunately they are probably not eligible to run locally.
@alvan @firefoxwebdevs They run locally, aside from the summarize feature, the sidebar and the search engine.
-
@raymaccarthy @plwt it's easy to say you don't have AI if you define it so it doesn't include features you have.
Folks consider translation to be generative AI https://mastodon.social/@firefoxwebdevs/115849251057488746
@firefoxwebdevs @raymaccarthy @plwt To be fair, the term AI has been so overloaded that it lost a lot of nuance. What most people hate with a passion are llms trained on data without permission, using up an insane amount of resources, while eroding people’s cognitive abilities by suggesting they eat rocks. And Mozilla saw this technology, and thought “let’s go all in on that”.
