Google Needs To Pay The Price For The Google+ Fiasco
By now you’ve heard that Google is shutting down their Google+ social networking site, at least to consumers as there’s a corporate version that will still exist, because of a a bug that put at risk the personal data of hundreds of thousands of Google+ users. What makes this worse is the bug was discovered months ago and Google decided to keep it quiet. Now Google does go into great detail about why Google+ is being shut down in a blog post. But what the blog post does not do is explain why the bug was hidden for months. For that, you’ll have to look at the Wall Street Journal who got their hands on an internal memo that explains that. Seeing as that is paywalled, Business Insider gives you the highlights of the leaked memo that basically says that Google buried this because they were afraid of the blowback from the US Congress over this. Not to mention the reputational damage that this would cause.
#EpicFail
Google hasn’t got the best reputation to begin with because they are a company that lives to collect data. So when something like this happens, it’s sure to garner more than its fair share of interest. And it should. If you as a company are going to collect personal information, you have the responsibility to keep it safe. Google didn’t in this case, and while it appears at first glance that nothing bad happened, they need to pay a price for the mistake and a higher price for the cover up. Neither is acceptable especially after the wake up call that the world got with the Facebook fiasco. Google really needs to step up and explain to the world why they should be trusted. Preferably in front of the US Congress or EU Parliament, and right before they slap them with penalties and enact legislation that forces them to do the right thing which is to protect the personal information of their customers. Seeing as they can’t or won’t do that on their own.
December 10, 2018 at 3:57 pm
[…] little while ago, it was disclosed that Google’s Google+ service had some serious vulnerabilities that would lead to the service shutting down. At the time I called it a fiasco, but now that fiasco […]