Today I realized (with @littlecalculist) that the web is AWESOME at dealing with low-disk-space situations (or just generally phones with little disk space).
Would this mean you would have to use the same origin for all content (what about fonts?)
-
-
Wouldn't need to be same-origin only, but all cookies, caches, etc. etc. would be effectively double-keyed. E.g.: `Content-Security-Policy: sandbox-storage; ...`
-
What would the effect of the double-keying be?
-
A big one would be that iframes of your origin outside of top-level loads would not include any of the state the user added in top-level navigation contexts.
-
I.e., the end of XSRF.
-
If it only affects credentialed content, BRING IT FUCKING ON
-
Would be all content. Why the credentialing difference?
-
https://twitter.com/slightlylate/status/983406442303471616 … I thought this implied that the "missing content" would be ~ credentials. What other state is important here?
-
All state would be unshared between the "isolated world" instances of an origin and the "regular world" ones. Service Worker registrations, cookies, other sorts of storage, etc.
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.