To be frank, I think the ship has already sailed. * Where were all these cryptography engineering folk when Google decided that it didn't have to ask any permi

To be frank, I think the ship has already sailed. * Where were all these cryptography engineering folk when Google decided that it didn't have to ask any permissions to install autoupdates to Chrome? * Subsequently, instructions were published on how to disable the autoupdate — published by Google itself, mind you — yet somehow after some time has passed, the same versions of Chrome that were supposed to have stopped looking for updates were somehow able to magically automatically update themselves in the end after a number of releases anyways — so much for the browser being secure against remote execution attacks by a powerful-enough party! BTW, if you think Brave is any better, they refused to disable the autoupdate. https://github.com/brave/browser-laptop/issues/1877 https://github.com/brave/browser-laptop/issues/1877 TBH, between the lines, I got the impression that it's part of the business plan, where an outdated browser is basically worthless to them as an investment anyways, so, spending any engineering resources on such causes is fundamentally not worth it. Who cares about the good-will of the user if there are so few alternatives anyways?! So, I basically stopped using Brave at that point, as I didn't feel like being the product. Mozilla may have gone away with asking for your permission to download and install the update as well, but at least there's still a clear setting in the interface which lets you be the boss, and, compared to the quirks that Brave may offer, at least once configured, you do know they won't go behind your back to do the dirty work anyways.