Maybe it's just me but why is it on by default? Why is this shit not off in the first place? Why can't Firefox just be a browser with great html, css, js rendering and then have a bunch of toggles for extra crap that people want? Do they actually have metrics that show "When we enable this crap by default we make an extra $X Million per year"? I'd put money on that being untrue. I bet it's like the data-driven ad spe…
Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
361–370 of 420 posts
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#362Earlier quoted context omitted.
Why do you actually ask? Switching browsers has got to be one of the easiest software to switch, right?
Is it? I have autofill/passwords, bookmarks, etc., and you can't easily jump between two different browsers as those will get out of sync.
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#363Earlier quoted context omitted.
If you don't add features that the average user might want, then yeah there won't be any more new users.
If you are competing with giants, you don't go after the average user but an under-served niche instead.
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#364Earlier quoted context omitted.
This UI is great but do you get this horrible thing where sometimes the browser is shows a white screen and you have to force stop the app? Happens all the time on the latest version for my Pixel 9a. And did on my Pixel 7 too before. It's really horrible and I can't pin down any rhythm or reason other than loosely seeming to happen more often when I'm in battery saver mode.
Are you using some weird extension ? Never had this on my pixel 6.
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#365What an absolute dystopia when disabling AI is considered a "feature". Obviously the _enabling_ of it should be the "feature" if anything, and considering popular opinion there is absolutely no reason to enable it by default.
> considering popular opinion there is absolutely no reason to enable it by default You need to update your priors. The popular opinion is there is a reason to enable it by default. ChatGPT is the #5 most popular website in the world, more popular than Wikipedia, Reddit or Twitter. The vast majority of users want to use AI. https://en.wikipedia.org/wiki/List_of_most-visited_websites
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#366Earlier quoted context omitted.
This UI is great but do you get this horrible thing where sometimes the browser is shows a white screen and you have to force stop the app? Happens all the time on the latest version for my Pixel 9a. And did on my Pixel 7 too before. It's really horrible and I can't pin down any rhythm or reason other than loosely seeming to happen more often when I'm in battery saver mode.
Happens to me all the time in PWAs. I get it roughly once in two days, sometimes a few times a day.
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#367Please let whoever steers Thunderbird development and road map also steer Firefox. Thunderbird is at the moment the pinnacle of user-centered, focused and down-to-earth development of open-source software.
You must be joking. The Supernova UI redesign is an unmitigated disaster. They unnecessarily butchered the look and feel of Thunderbird to the point where people are switching to forks.
Give me the 1990s GUI back.
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#368Earlier quoted context omitted.
Approximately all people update Firefox so you don't need telemetry to count "AI disabled" installations, instead you can derive it as "updates requested" minus "AI enabled".
But the AI and telemetry toggles aren't coupled. While we can assume that users who disable telemetry are more likely to have AI disabled as well this still isn't translating to user numbers.
Re: Firefox 148 Launches with AI Kill Switch Feature and More Enhancements
#369Earlier quoted context omitted.
I wasn't aware of the "-ai" flags. Good to know. Do you have a preferred way of blocking domains from appearing in search results? I think there's a limit of only five for some reason.
> Do you have a preferred way of blocking domains from appearing in search results? Paying for Kagi which lets you promote/demote/block domains to your heart's content.