4 ms·
But auto-update would require not only telemetry but remote system administration capabilities too. You'd have to monitor people's browsers to make sure a chang
by jart 5y ago
But auto-update would require not only telemetry but remote system administration capabilities too. You'd have to monitor people's browsers to make sure a change you made isn't causing everyone's browser to break. In the event that it does, you'd be able to halt the incremental rollout before it impacts too many people.
- account42 5y ago> You'd have to monitor people's browsers to make sure a change you made isn't causing everyone's browser to break. In the event that it does, you'd be able to halt the incremental rollout before it impacts too many people. Just let people install the update when they want (so they can make their own decisions on the risks) and provide ways to get feeback to you if there are problems. No need for telemetry at all or even an explicit incremental rollout when you don't force users to update.
- jart 5y agoI agree, however there's more wisdom to that strategy if you're working with a novel technology stack like the SerenityOS browser. Chrome and Firefox are lucrative enough as targets that weaknesses are exploited in the wild rapidly enough that people are willing to make that bargain with internet leviathan on auto-updates. Something like LibreWolf has that same target painted on its back, but it's not the devil you know. On the other hand, SerenityOS is kind of like how back in 2003 when all the bad guys started targeting Windows users en masse, everyone switched to Linux, and then the whole virus issue went away. Not because the scrappy Linux developers were wiser and had better security practices than Windows, but rather it was just simple economics.