Re:Bypassing anti-incognito detection in Google Chrome
by TomAnthony on Saturday July 20, 2019 @04:04AM
(#20484673)
I believe the “Quota Management API” [1] the author is using is an experimental API for the browser to request more space, beyond the default maximum of 5MB.
Re:Bypassing anti-incognito detection in Google Chrome
by geekroutine on Saturday July 20, 2019 @04:22AM
(#20484719)
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 development.
[1]https://w3c.github.io/quota-api/
[2]https://storage.spec.whatwg.org
Re:Bypassing anti-incognito detection in Google Chrome
by dTal on Saturday July 20, 2019 @08:53AM
(#20485453)
In a distributed environment like the web, how do you define an 'app'? If the restriction is e.g. 10MB per domain, what stops an entity registering a hundred domains?
Re:Bypassing anti-incognito detection in Google Chrome
by zzo38computer on Sunday July 21, 2019 @01:55PM
(#20492628)
One possibility is to require the user to explicitly set up an "app", to allow the user to specify the limits independentlyf or each one, to allow the user to put multiple domains into an app if they wish, and to allow the user to define multiple apps for a single domain in case they want to have separate sets of data to send in different cases.
I'm becoming increasingly wary of web apps having all sorts of access to things outside of the browser, sometimes without explicit permission. Browsers should limit every app to the same amount, perhaps 100MB, or maybe even 10MB. Apps that need more should ask for permission.