@firefoxwebdevs
For wording: [remove all] would match the intention you’re describing (the antonym of provide¹). And added

"default for future features: (available / unavailable)"

But not to be misunderstood:
I like it that you’re giving the option to disable all of them together. It’s just the way of implementation that feels so wrong.

It feels like FF is making a fuss about me stating my preference.

¹ https://www.powerthesaurus.org/provide/antonyms

2/2

@firefoxwebdevs @plwt
Unfortunately no-one is trustworthy. The results are dubious and entire page via browser (tested in Chromium & Firefox) is misleading and a privacy horror.

Hence I'll copy / paste fragments for translation.
A web browser should NOT be a platform, but simply render web pages for screen or "print" (which might be PDF).
Print is still abysmal.

Also it's obnoxious that the browser GUI ignores the OS GUI / theme/style and imposes an idiot one.

@firefoxwebdevs And I’ve really taken up enough of your time with this.

All I wanted to do was to give you user feedback on the UI. I did that now.

I didn’t want to spread aggression (though I got too emotional) or speak against the block option in general.

I know that UI is hard and that making UI choices that touch a heated societal debate is doubly so.

To sum it up: I’m sorry for stress I caused.

/cc @dveditz

@raymaccarthy @firefoxwebdevs The recent survey was not from the Mozilla Corporation (that makes Firefox), but from the Mozilla Foundation. I would not expect it to mention Firefox.

@raymaccarthy @firefoxwebdevs Catering for every UI would make maintaining the features that people like to use much more challenging.

@firefoxwebdevs I wonder how many people will still complain…

//checkes the comments

that's about right - tiny vocal minority is still absurdly butthurt…

@fabio @firefoxwebdevs survey only shows a tiny fraction of the total userbase. why it should influencethe default?

@plwt @firefoxwebdevs
No it's simpler. unless you are using a broken framework. I was writing desktop SW 15 years ago and without ANY extra work it used the Mac, Redhat, Ubuntu, XP or Vista theme in use.

Most programs on XP, Win7, Win10, Linux etc use the current theme.

@plwt @firefoxwebdevs
It was a survey about inclusion of AI that didn't ask if it was even wanted.

It's disingenuous to suggest it's not related to Firefox.

@ArneBab @firefoxwebdevs @dveditz agreed with everything save for your apology. From the conversation, you were making your point rather clear & the response you got was evasiveness & gaslighting, so of course you'd get heated.

@kittyjynx @firefoxwebdevs
> a browser not infected with Google, Apple, and now Firefox code

Pale Moon? https://en.wikipedia.org/wiki/Pale_Moon

@firefoxwebdevs I mean ... as much as I appreciate the transparency for the sort of people who follow release notes and developer channels, the whole idea of putting this is a user-friendly and straightforward settings page is to help the un-tech-savvy users who don't.

Like, both my wife and my kid use Firefox and they're NEVER gonna read a release note.

@mausmalone also, the way this button is being presented feels like we are enabling a sparkly new thing? Kind of the opposite of what it is doing

@firefoxwebdevs

@raymaccarthy @firefoxwebdevs Apologies, I am not trying to be disingenuous. There was a survey recently from the Mozilla Foundation that was looking at their future work. Many people seem to think it was tied to Firefox.

@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.

@Ostrobothnia @firefoxwebdevs Thanks for the rec! I just installed it and will be test driving for a bit!

@firefoxwebdevs yay! \o/

@firefoxwebdevs

What Mozilla did: ️

What the users actually wanted: ️

Duke of Germany 💫 (@duke_of_germany@mastodon.gamedev.place)

Let's ask the real question: Firefox users, do you want any AI directly built into Firefox, or separated out into extensions? @firefoxwebdevs@mastodon.social @davidgerard@circumstances.run @tante@tldr.nettime.org #Firefox #InformedConsent [ ] I want AI built into Firefox [ ] I want AI separated into extensions [ ] Mozilla should not focus on AI features at all

Gamedev Mastodon (mastodon.gamedev.place)