geekroutine

4 ms·

1. 1.▲
   A Simple Homemade JavaScript Obfuscator(antoinevastel.com)

   3 points by geekroutine 7y ago|0 comments
2. 2.▲
   by geekroutine 7y ago

   I think chrome devs want to limit the "file system imprint" as much as possible to enforce "no-history in incognito". There's been some discussions on finding a way around crash reporting in incognito session which
3. 3.▲
   by geekroutine 7y ago

   On the contrary its on active development, The one you are referring to "Quota Management API" [1] is not what's being used in the article. It's the "Storage" API's Estimate method [2] which is in active d
4. 4.▲
   by geekroutine 7y ago

   It's still detectable, this protection introduces a new side-effect which can be used to detect incognito. I Wrote a blog post[1] yesterday showing how to do that. [1] http://mishravikas.com/articles/2019-07/by
5. 5.▲
   Bypassing new Chrome anti-incognito/private mode detection(mishravikas.com)

   5 points by geekroutine 7y ago|0 comments