31 ms·

Is it there fault if you don't read? or it your fault? Likewise... who's to blame if a rogue addon isn't responded too? Same arguments get bundled about stuff

Is it there fault if you don't read? or it your fault? 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.

starttoaster 3y ago
> Is it there fault if you don't read? or it your fault? 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.
Hizonner 3y ago
> Is it there fault if you don't read? or it your fault? 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.
kelnos 3y ago
> Is it there fault if you don't read? or it your fault? 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.