Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"It is magical because it continuously updates an entire development platform invisibly, frequently"

That "frequently" is every 30 minutes, by the way... I accidentally removed the goog updater from my Lil Snitch rules and noticed that it then started asking permission every 30 minutes, on the dot (I started recording the times for a while).

I don't know why it needs to check so often - except that that kind of data would be very useful for noting how often your users were on 'puters, and if they moved around etc.



Out of curiosity, were you allowing it to check? If you denied permissions I could see it asking every 30 minutes since it failed the previous attempt.


A hyper short time could be massively benefitial to security. Imagine a security bug fix that's installed on every browser within the hour.


That is true... but it can go the other way to: Imagine a security bug that is introduced on every browser within the hour.


Even worse: imagine a poisoned update that gets installed on every browser within the hour.

Or just an update with a non-malicious bug that breaks the updating mechanism. (This last has happened to companies the size of McAfee and Skype.)


In this case the benefit far outweighs the cost, if a bug is introduced in an update I want Google to be able to patch it and my browser to receive it asap.


Yes, that would be a problem, but it would have an easy fix, revert!


I think that must be once in 30 minutes polling not once in 30 minutes updates.


Just curious - when does it do its first check? Immediately upon launch, or after 30 minutes of wait?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: