Chrome Updated Incognito Browser

Today it seems like Chrome tends to rule the land of, well, everything. It tracks and contains data from its own sources and it tends to put a lot of its users a little uneasy at the idea of all that flows through chrome. A lot of other browsers put a good amount of effort to protect you from outside data and breaching, and chrome is no exception to that.

Google recently updated their privacy policies and are actively seeking advanced techniques to protect their users, even from collecting site data and information. It's sort of strange that a company that specializes in search queries is trying to protect site data from collecting information about you. Well, I imagine the tech giant tends to keep your data to itself in the long run anyway. After all, that is how they make money... Even if the entire supreme court doesn't understand how facebook was able to make money off "just ads" - Little do they know billions of dollars flow through targeted marketing.


Targeted marketing is insanely advanced and while you might think there is some mastermind genius on the other end of your keyboard collecting data and using it to target ads, I promise you that it's only a collective of nerds learning deep learning and AI. Before I ramble on too much, let's talk about some of the privacy updated that chrome implemented.

Google references the W3C TAG Observation on Privacy Browsing Modes which states that "Developers of new web features should consider how those features might need to differ in private browsing modes. Given that these modes vary between implementations, the way a feature differs in private browsing mode may also be subject to variation between implementations. Because of this, specification regarding such differences may need to be informative rather than normative. Describing these differences in specifications is still valuable because it encourages implementers to consider the issues involved, and it shares the expertise of the specification authors."

This statement is extremely imperative to the way chrome decides to implement updates to private browsing. Google states that they will fix the FileSystem API Loophole in private browsing. "Today, some sites use an unintended loophole to detect when people are browsing in Incognito Mode. Chrome’s FileSystem API is disabled in Incognito Mode to avoid leaving traces of activity on someone’s device. Sites can check for the availability of the FileSystem API and, if they receive an error message, determine that a private session is occurring and give the user a different experience.  

With the release of Chrome 76 scheduled for July 30, the behavior of the FileSystem API will be modified to remedy this method of Incognito Mode detection. Chrome will likewise work to remedy any other current or future means of Incognito Mode detection."


Basically, sites detect private browsing and it acts differently because of it, which in some cases may be (in a way) discriminative to the users experience - such as bank pages or online stores. If you aren't able to use these sites the way they are intended, then why bother even going into incognito mode to begin with? - This is the issue.


As you can see, Google is more interested in its ethics rather than the idea. They think of it more as a way of life, rather than something they have to do. Something that even other big web browsers struggle to realize. Yes, I am looking directly at you EDGE you son of a...

Google states: "We want you to be able to access the web privately, with the assurance that your choice to do so is private as well. "

What do you think? Leave a comment below if you are a member, and if you aren't yet, well It's free and we don't sell your data or use ads, so what are you waiting for?

151 views0 comments

Recent Posts

See All