scrib Tom T.Somehow, they survived F2 and F3, with a "notify me", so they could install when convenient, and not necessarily in the middle of a session.
That may not be instantaneous,
The central point about a fully transparent service isn't its timeliness so much as its transparency. Social engineering has followed the money with malware "alerts" so when the anxious, alert, but non-tech user encounters one of these ↓
and they're trained to react to all the security theatre that's around on the web now, are you so sure that they won't be reacting to some clever social engineering?A notification screen, perhaps with a special screen for in-the-wilds -- "THIS UPDATE FIXES AN URGENT SECURITY FLAW" -- but don't cry wolf when it doesn't. For less-urgent, the prompt lets the user update at their earliest convenience.
Did you read my description of most folks' reaction to notifications? I'm not a coder or employed by Mozilla. I experience very different to what you report with non-tech folks; they want someone to set it up so they don't have to make decisions about which they feel unable to have enough knowledge themselves. They've been warned time after time *not* to react to notifications without being completely sure they know what's happening. The browser is a complicated bit of machinery and they want nothing to do with what's under the hood. All they want is a good mechanic. And sadly for most owners of Win machines, they are out on their own after making the purchase unless they have the funds to purchase a tech to look after it.
So I don't agree with you.
Better to have the new service on by default with a new install, but certainly there should be a splash notification of such with any updates so the worried user like yourself would be able to opt out. For exactly the reason I've been arguing: give a novice a reason to ignore some technical notification and they will happily ignore it. A splash page about a background service that they could turn on? TMI. Leave it until they can ask a tech......in the meantime zero days etc etc. I think this is a great move by Mozilla. They're out there taking full responsibility for their web users. Why ever would they go to these lengths of control of the browser in Win machines and not any other OS, do you think? It's not as if Mozilla aren't capable of doing the same for OS X, and other unixes, but there's no equivalent service getting added to their versions. Something to do with the vast majority of browsers being in Win machines, plus Win not having a trusted repository for third-party software, unlike other popular systems. Fx 2 and 3 users in any of the linux distros were already used to having this kind of service running.
The argument about earlier Firefoxes not needing this service is a little disingenuous; Mozilla have judged that they can provide the service now. They didn't judge they could provide it before now. Maybe they could've provided the service for previous versions but chose not to because the tipping point of Win user quota didn't justify it until now? Web2 has made a hell of a lot of people into facebk and twidder morons, so I prefer to analyse Mozilla's actions in this instance as a community-minded attempt to stop the rot.