Comment #27 on issue 1565 by alf.p.steinbach: Don't make GoogleUpdate always-resident http://code.google.com/p/chromium/issues/detail?id=1565
I note that the team's arguments are of the sort "We need to do it this way because we can imagine some silly ways that Won't Work". That's usual corporate evade the issue, deflect, be very oily snake that gives appearance of being sympathetic to the concerns raised, but always with Do Nothing. Which causes at least me to wonder (1) are Google developers incompetent, unable to think of methods that work, and so amnesiac that they can't remember that solutions that work have been suggested, as above, *or* (2) do they have some other reason for hiding this always running beast, hiding its files, hiding that it's there, hiding its invocation mechanisms, not providing removal capability, ensuring that it will always re-activate even when killed, and so on, all hallmarks of spyware and other malware? After I found this hidden beastie I've googled :-) around, and it seems it hooks its claws into your machine's back in at least four ways: (1) Run-key in registry (on my machine), (2) scheduled tasks (on my machine), (3) Firefox extension (reported elsewhere) and (4) some service (reported above). My trust in Google is now near to non-existent. That's after earlier I found that Google engages in earlier Microsoft practice of giving the appearance of letting you report bugs, but where those pages just lead to cul-de-sacs everywhere. That concerned bug in Google Earth (placing Norway in Sweden), which I don't know if is there still, no way to report; bug in Google Groups (the sh*itty interface actively destroys signature delimiters, what the heck is the purpose of such inane action, if not to sabotage Usenet to promote Google's own group); and some bug in Google Talk. Paradoxically, the evil empire, Microsoft, now, since a few years ago, instead actively try to collect bug reports and do something about them in transparent way. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
