In the release notes which 95% of users don't read, and in a text label hidden in a toolbar menu. No informed consent or prompt to opt-in. And Mozilla hasn't disclosed their criteria for inclusion of websites, and what they plan to use it for.
I agree with you that Mozilla has certainly dropped the ball regarding this change. Much like pocket, the Mr Robot ARG, the Quantum update, DoH with Cloudflare as the default provider, and so on. But again all but the Quantum update have been user configurable, and in my experience, have not been reverted unlike my browser preferences on Windows, where Edge hijacks anything and everything with very little recourse.
that's... not a valid argument for this discussion? market share and user conservatism has no connection to concerns about basic safety affecting everyone
judgement should be applied equally, every user and every product
I believe the intention was to argue against the notion that 95% of users don't read release notes. The contention seems to be that, because Firefox users are more technical (or enthusiast, perhaps), more than 5% of Firefox users would read be aware of this change.
Now I agree that this change is not being communicated properly but to claim that the Firefox user is similar to the average computer user is not something I would agree with.
Is Mozilla content with that market share? If not, it must act with the assumption that its users are average.
Are users giving informed consent for Google's ability to remotely disable Android apps or Apple's ability to do the same on iOS?
The ability to disable malware as it is discovered seems to be a very common pattern.
If you include the bundled malware scanners on MacOS and Windows, it's taking place on them as well.
No, but we expect Google to be user-hostile. We expect the opposite of Mozilla.
This feature does seem like it's designed to help defend against bad plugins, but in other hands it could be a source of worry.
Likewise... who's to blame if a rogue addon isn't responded too?
Same arguments get bundled about stuff for iOS and it's absolutely responsible for companies to be proactive about issues with stuff like automatic updates because failure to do is, in aggregate, is worse because of stuff like zero days.
I don't know their exact argument, but I would assume a better place for a notice like this would be a popup or some kind of tiny tooltip window when you update to Firefox 115 that says "hey, we can disable an extension at any time if we find reason to believe they're acting untrustworthy and misbehaving, you can disable that behavior by going here."
I cannot fathom how someone would disagree with this user experience suggestion around this new feature.
I guess I need to read every line of the source code, too. After all, they publish the code, so that's fair warning.
> Likewise... who's to blame if a rogue addon isn't responded too?
The person who chose to install it.
Given that Firefox auto-updates, and most of the time doesn't put up a "What's New" type page after the update installs, I don't think it's reasonable to expect that most users would even know that there's a separate release notes page, let alone that they should read it.