[ad_1]
<div _ngcontent-c14 = "" innerhtml = "
Getty
Google+ has never really emerged as a social media competitor to beat the likes of Facebook and Twitter that Google had hoped for. Today, less than eight years after its launch, Google+ has officially stopped being. Google said that from today on, the content of Google+ Consumer Accounts will begin to be removed. There are many reasons that could be drawn from the reasons for the closure of the hat, including the fact that it was a vacant lot rather than a thriving network, but the The last straw for this social camel was actually a coding bug with implications for the privacy of the user.
While Facebook has up to now largely weathered the storm of user privacy issues, Google+ had neither the critical mbad of staff nor the momentum of the community to survive the potential exposure of 52 million users. Google itself admits that Google+ was a failure, the consumer version with "low usage and commitment" 90% of Google+ user sessions are less than five seconds. But it was the combination of this bug, and the decision not to disclose it for several months, which really hit the nails in this coffin.
The coding bug was supposed to be active between 2015 and 2018, leaving profile information such as gender, age, occupation, and so on. similar to third-party developers, even if they were reported as confidential by the user. It was finally discovered and repaired in March 2018, but it was not until October that Google became a virgin and divulged it. The decision to delay disclosure was in part, according to the Washington Post report, according to which broke the news, "as this may result in regulatory scrutiny and damage to the reputation of the company."
This should be a lesson for all organizations: in terms of privacy and user safety, honesty and urgency are the best rules. Some repercussions on reputation would inevitably have occurred, but they would probably have been short-lived and relatively easy to contain. Indeed, while Google admitted this "the bug has affected about 52.5 million users" he also pointed out that there was no evidence that any of the hundreds of developers having access to this user data for six days really know it and even less have abused it. According to Ben Smith, a Google colleague and vice president of engineering, the final figures It turned out to be 438 apps that used the buggy code that potentially gave access to "up to 500,000 Google+ accounts" rather than exceeding 50 million.
If you used Google+, you had ample time to back up your content and the detailed instructions Google provided to do so. However, if you have managed to miss all this, it is probably not too late to access your messages. the Internet Archives has backed up public publications in recent weeks, with images and videos stored at a low resolution, and you can see how that goes with the courtesy of a tracker in real time.
Google+ is not completely dead though. Business users will be happy to know that it is still part of Google GSuite as an internal communications network. For everyone, being brutally honest, I do not see many tears flowing …
">
Google+ has never really emerged as a social media competitor to beat the likes of Facebook and Twitter that Google had hoped for. Today, less than eight years after its launch, Google+ has officially stopped being. Google announced that, as of today, the content of Google+ consumer accounts would begin to be removed. There are many reasons that could be drawn from the reasons for the closure of the hat, including the fact that it was a vacant lot rather than a thriving network, but the The last straw for this social camel was actually a coding bug with implications for the privacy of the user.
While Facebook had so far largely weathered the storm of user privacy issues, Google+ had neither the critical mbad of membership nor the momentum of the community to survive. potential exposure of 52 million user data. Google itself admits that Google+ was a failure, with the consumer version having "low usage and engagement" and 90% of Google+ user sessions taking less than five seconds. But it is the combination of this virus and the decision not to disclose it for many months that have truly hit the nails of this coffin.
The coding bug was supposed to be active between 2015 and 2018, leaving profile information such as gender, age, occupation, and so on. similar to third-party developers, even if they were reported as confidential by the user. It was finally discovered and repaired in March 2018, but it was not until October that Google became a virgin and divulged it. The decision to delay disclosure was partly, according to the Washington Post report that announced the news, "because of fears that this will result in regulatory control and damage to reputation."
This should be a lesson for all organizations: in terms of privacy and user safety, honesty and urgency are the best rules. Some repercussions on reputation would inevitably have occurred, but they would probably have been short-lived and relatively easy to contain. Indeed, although Google admitted that "the bug affected about 52.5 million users", he also pointed out that there was no evidence that hundreds of developers with access to this user data for six days really became aware of it and misused it. According to Ben Smith, a Google member and vice president of engineering, the final numbers turned out to be 438 applications using the buggy code that potentially allowed to access "more than 500,000 Google+ accounts" instead more than 50 million.
If you used Google+, you had ample time to back up your content and the detailed instructions Google provided to do so. However, if you have managed to miss all this, it is probably not too late to access your messages. Internet Archive has been backing up the publicly available publications for a few weeks. Images and videos are stored at a low resolution. So you can see how it works with a real-time tracking tool.
Google+ is not completely dead though. Business users will be happy to know that it is still part of Google GSuite as an internal communications network. For everyone, being brutally honest, I do not see many tears flowing …
