The Truth About Google To Make Chrome’s Incognito Mode More Private Is About To Be Revealed.

The Truth About Google To Make Chrome’s Incognito Mode More Private Is Beacuse of the arrival of Chrome 76 at the end of July brings with it an update that will close an "unintended loophole" that has been near the browser's Incognito mode for some time.

Once this latest release is released, a method that websites use to check if a visitor is in incognito mode becomes unusable.

FileSystem API

In a blog post that was published on July 18, Google announced that it will close the gap in FileSystem API with the release of Chrome 76. The FileSystem API is disabled for private browsing and websites can check if the FileSystem API is available to determine whether a user has visited the site in Chrome incognito mode or not. If it is not available, it means that a visitor is in private mode.

According to Google, when a site detects or a user surfs through incognito mode, he asks visitors to open the site with a regular Chrome browser. Some sites do this to count how many site visits they have had over time.

"With the release of Chrome 76 scheduled for July 30, the behavior of the FileSystem API will be adjusted to fix this incognito mode detection method. Chrome will also work on fixing other current or future incognito mode detection methods," Barb Palser, Partner Development Manager, News and Web Partnerships at Google, said.

True private navigation in incognito mode

At first glance, this seems like a huge blow to the incomefrom publishing sites. However, Google said that this change is all about maintaining privacy, because this loophole is better than the purpose of Chrome's incognito mode.

While it is true that some users browse privately to avoid payment walls, some users have a more serious reason why they opt for Incognito browsing. An example would be if a user wants to keep his internet activity private to prevent political oppression or if he tries to avoid someone who is offensive.

Some users even browse privately when borrowed devices are used to not affect the web preference of the device owner. Another reason is to exclude certain sites from a user's browsing history and activity.

All in all, Google urges publishers to "check the effect of the FileSystem API change before taking reactive measures."
Share on Google Plus



Completely Sponsored Australian Government Scholarships for International and African Students In Australia, 2019

Fully Sponsored United States of America Embassy Scholarship Award for International Students to study in USA 2019

Microsoft Pays Hackers $30,000 To Find Errors In The New Edge Browser