Google Fixing Chrome API To Prevent Incognito Mode Detection (bleepingcomputer.com)
AmiMoJo writes: When browsing the web with Google Chrome, some sites are using a method to determine if a visitor is in a regular browsing session or in incognito mode. As this can be considered a breach of privacy, Google will be changing how a particular API works so that web sites can no longer utilize this technique.
Chrome supports the FileSystem API, which allows sites to create a virtual file system that lives within the sandbox of the browser. This allows sites that utilize large assets, such as online games, to download these assets to a virtual file system so that they do not have to download them each time they are needed. Currently the FileSystem API is not available in incognito sessions, because it leaves files behind and could be considered a privacy risk. Currently the API doesn't work in incognito mode, offering sites a way to check for it. In a Chrome Gerrit post started this week and updated earlier this morning, Google has stated that they are changing the FileSystem API so that it can be used in incognito mode, without the risks to privacy.
Chrome supports the FileSystem API, which allows sites to create a virtual file system that lives within the sandbox of the browser. This allows sites that utilize large assets, such as online games, to download these assets to a virtual file system so that they do not have to download them each time they are needed. Currently the FileSystem API is not available in incognito sessions, because it leaves files behind and could be considered a privacy risk. Currently the API doesn't work in incognito mode, offering sites a way to check for it. In a Chrome Gerrit post started this week and updated earlier this morning, Google has stated that they are changing the FileSystem API so that it can be used in incognito mode, without the risks to privacy.
This story makes no sense. Slashdot assures me that Google is evil and hates privacy, yet here they are doing something to improve privacy.
It makes about as much sense as that time they tried to ban ad-blocking by introducing a new high performance ad-blocking API built right into the browser, and then listened to feedback and decided to keep the old one around for good measure, even though they hate ad-blockers and live for ads.
Can someone explain this latest move, preferably with an outlandish conspiracy theory about how Google is secretly taking over the entire internet and all this privacy/ad-blocking stuff is just to drive all rivals out of business so they can get to the anti-trust break-up stage as quickly as possible.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
TFA "Since the data is kept in memory in the browser process, a malicious website could try to exhaust the memory of the browser process and make it more likely to crash"
Google is the best at algorithms, how could they miss checking such an obvious trait and ensure the FS does not go over x MB?
Slashdot, fix the reply notifications... You won't get away with it...
This has been known for several years (https://stackoverflow.com/questions/2909367/can-you-determine-if-chrome-is-in-incognito-mode-via-a-script)
There are plenty of other methods to check whether or not you're in incognito mode (http://www.collinjackson.com/research/private-browsing.pdf)
Custom electronics and digital signage for your business: www.evcircuits.com
Many news sites let you have a few free articles every month. The number gets reset if you clear your cookies, but if you read in incognito mode, you start fresh every time. Taking this into account, I've hit one news site that simply blocks incognito mode. I'll be happy if this breaks their block.
Of course, with the vast number of APIs available now, fingerprinting is just about as good as cookies. Browsers reveal far too much information.
Can you please put the option to put the tabs and blinding white off back to where it was at version 70?
I still use that version as I get migraines easily and it's hard to differentiate tabs with my multiple monitors
http://saveie6.com/
If "incognito mode" is your idea of privacy, this won't change your status from Sucker
If you want to browse the web anonymously, forget it. No matter what tricks you use, you can be tracked. Sure, some methods of going incognito are better than others, but when it comes down to it, don't ever, ever trust that what you are doing on the Web can't be found out.
If Chrome has plans to remove the FileSystem API if it sees no legitimate use outside of the aforementioned discovery technique, would this have any impact on the FileReader API in any way shape or form? I only ask this as the FileReader API is key component of a major web project of mine.
They're not removing the API, quite the opposite. They're making it available in private mode, where it isn't currently.
Many news sites let you have a few free articles every month. The number gets reset if you clear your cookies, but if you read in incognito mode, you start fresh every time. Taking this into account, I've hit one news site that simply blocks incognito mode.
Was it MIT Technology Review? If so, I think it was testing for existence of third-party analytics/advertising ID cookies, not any file system API. I don't use incognito per se, but I have encountered that message while using Firefox built-in tracking protection, which blocks URLs known to be involved in cross-site interest gathering. (It uses the same list as the Disconnect extension.)
I'll be happy if this breaks their block.
If a paywalled site doesn't detect a third-party analytics/advertising ID cookie, it may require the user to log in through Facebook, Google, Twitter, GitHub, or the like so that such a cookie can be dropped.
Subsequently I saw this article that seem to indicate there was a stance to potentially remove the API all together if Chrome sees fit. https://www.theverge.com/2019/...