here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
-
the problem is going to be for how long can LibreWolf keep up with stripping the slop out of each release? at what point do they just burn out and call it quits?
@cerement I agree, fleecing all the incoming commits, outright avoiding or digging out the asbestos/microplastics/plutonium afterwards, must be a metric shitton of work, git and proper PR workflow notwithstanding. No rush wrt "features" though, and the relevant security fixes should be possible to fast-track. I must admit, I have no practical experience in that particular project, might wanna look into it though. @zzt @fasterandworse
-
@zzt i def agree that that’s their goal. but like, what does it do today? is opening a New Classic Window the same as opening a regular new window? how unnecessary and confusing
@mrs_malice I just tried to re-enable it to try and the menu items wouldn’t come back. I noticed Firefox bounced longer than usual so maybe it updated and I’m no longer in the group that got these menu items? bizarre shit.
-
@mrs_malice I just tried to re-enable it to try and the menu items wouldn’t come back. I noticed Firefox bounced longer than usual so maybe it updated and I’m no longer in the group that got these menu items? bizarre shit.
@mrs_malice and of course there’s nothing in Firefox Labs but that’s not unexpected; Mozilla’s no longer upfront with experiments and staged rollouts because that means their users could say no
-
@mrs_malice and of course there’s nothing in Firefox Labs but that’s not unexpected; Mozilla’s no longer upfront with experiments and staged rollouts because that means their users could say no
@zzt no consent! only comply!!
-
here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
these showed up in my File menu, displacing the New Private Window item and fucking up my muscle memory, in spite of having browser.ml.enabled set to false. the setting for this is a new nonsensically named option, extensions.ml.enabled. a merry fuck you to the guys who showed up in my replies telling me to just disable the config flag I already disabled months ago.
@zzt
Servo can't reach parity fast enough. -
here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
these showed up in my File menu, displacing the New Private Window item and fucking up my muscle memory, in spite of having browser.ml.enabled set to false. the setting for this is a new nonsensically named option, extensions.ml.enabled. a merry fuck you to the guys who showed up in my replies telling me to just disable the config flag I already disabled months ago.
@zzt so far my migration to Vivaldi browser has been pretty painless. I liked Firefox, but Vivaldi for right into my workflow with no issues.
-
here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
these showed up in my File menu, displacing the New Private Window item and fucking up my muscle memory, in spite of having browser.ml.enabled set to false. the setting for this is a new nonsensically named option, extensions.ml.enabled. a merry fuck you to the guys who showed up in my replies telling me to just disable the config flag I already disabled months ago.
-
@cryptica oh that’s incredible
-
P Pteryx the Puzzle Secretary shared this topic
-
@cryptica oh that’s incredible
@zzt Just a little something I threw together the last time folks on retropizza came together to yell at firefox
-
here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
these showed up in my File menu, displacing the New Private Window item and fucking up my muscle memory, in spite of having browser.ml.enabled set to false. the setting for this is a new nonsensically named option, extensions.ml.enabled. a merry fuck you to the guys who showed up in my replies telling me to just disable the config flag I already disabled months ago.
@zzt Just like Chrome, hard coding that shit so no options can disable it.
Fuck Mozilla. They betray their users.
-
@zzt
Servo can't reach parity fast enough. -
here’s a worked example of why nobody believes firefox’s AI kill switch will be anything but a marketing wedge
these showed up in my File menu, displacing the New Private Window item and fucking up my muscle memory, in spite of having browser.ml.enabled set to false. the setting for this is a new nonsensically named option, extensions.ml.enabled. a merry fuck you to the guys who showed up in my replies telling me to just disable the config flag I already disabled months ago.
@zzt serious question: what the heck is a “New AI Window” exactly?
-
@cerement I agree, fleecing all the incoming commits, outright avoiding or digging out the asbestos/microplastics/plutonium afterwards, must be a metric shitton of work, git and proper PR workflow notwithstanding. No rush wrt "features" though, and the relevant security fixes should be possible to fast-track. I must admit, I have no practical experience in that particular project, might wanna look into it though. @zzt @fasterandworse
@ulfr @cerement @zzt @fasterandworse “I don’t really have any experience about any of this, but I think it’ll be fine!” perhaps you should have thought more before making your post?
I *do* have some experience in this domain (and have even gone through the Fx source to a moderate degree), and that’s why I don’t think there’s much of a future in librewolf etc. same as why the chromiums don’t maintain mv2:
the big outfit can employ attrition against small teams, and *very* effectively
-
J Jürgen Hubert shared this topic
![[object Object]](https://media.mas.to/accounts/avatars/109/287/758/133/964/366/original/0f3099c0adfb36a0.png "[object Object]"){kind=avatar}
I know it's not what you meant, but I do agree with you on what you mean.