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).
-
Show this thread
-
One major contributor: browser vendors have zealously guarded the right to evict things from the cache as needed, and according to algorithms of their choosing, even with the advent of PWAs.
3 replies 1 retweet 7 likesShow this thread -
Replying to @wycats
It has required many tradeoffs, and we still need to make more of a given disk available to web apps, but this is a key part of why web has good EM product/market fit (when we don't drown in JS)
1 reply 0 retweets 2 likes -
Replying to @slightlylate @wycats
I’m still not sure why we don’t have a simple “is x in browser cache” method though. Why is that hard?
2 replies 0 retweets 0 likes -
It's shared. Deep privacy implications.
1 reply 0 retweets 2 likes -
1 reply 0 retweets 1 like
-
Heh. One way I think about this is that we could add such an API if the HTTP cache weren't shared across origins. Such a cache would be less useful in some ways, but better in this way.
1 reply 0 retweets 1 like
And we might end up there. Timing information leaks some knowledge, but leaves room for policy-based intervention (i.e., can skip caches for things we suspect are for tracking)
-
-
This Tweet is unavailable.
-
Replying to @sayrer @slightlylate and
I think we could whitelist our non-authed asset cdn.
0 replies 0 retweets 0 likes
End of 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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.