I think when I (or someone else) says the word “enhancement” what you hear is “*just* an enhancement”—I think that may be at the heart of your Colombo-like feigned confusion.https://adactio.com/notes/16625
-
-
Popping up a bit, a slightly more generous way to read Apple's new policy is that it degrades their (already bad) web storage limits to the point where the _only_ safehaven is installation to the homescreen.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @adactio and
This is inline with Chrome (et. al.'s) construction of a two-tier system, wherein sites that are installed get "more" in various ways. We've been careful not to break things between these modes, and only hang app-mode enhancements on installation, not basics (like storage).
1 reply 0 retweets 4 likes -
Replying to @slightlylate @adactio and
What's different here is that Apple is explicitly making web-in-a-tab non-durable, whereas we've *enhanced* the durability of web-in-a-tab recently.
2 replies 0 retweets 4 likes -
maybe I am misreading your and
@wanderview's replies. That would clear a lot. *Specifically* if you could answer just y/n: other than specific details abt durability/storage differences, is this fundamentally different than ff/chrome in 2 tiers/durable not permanant/use matters?1 reply 0 retweets 0 likes -
Replying to @briankardell @adactio and
At the limit they are the same (origin-wide eviction under pressure). What's different is that we aren't trying to apply more pressure, so incidence of eviction is *wildly* different. In all cases, if users want to keep it, we need to get them to add to install.
3 replies 0 retweets 4 likes -
Replying to @slightlylate @briankardell and
I think there is a big difference between evicting under storage pressure (legit resource constraints) and deterministic wiping after arbitrary time periods.
1 reply 0 retweets 6 likes -
Replying to @wanderview @slightlylate and
Specifically: Why and how it chooses to apply time to the equation in browsers (not running as pwa) is the only difference tho, right? Just confirming that I understand correctly before I ask one more question..
1 reply 0 retweets 0 likes -
1 reply 0 retweets 1 like -
Replying to @adactio @briankardell and
Jeremy, I see what you're saying, but there's an important mis-communication in your blog post that
@briankardell is clearing up: https://adactio.com/journal/16619 You say "Caches, Local Storage, Indexed DB—all of those are subject to eventually getting cleaned up." ...but *atomically*2 replies 0 retweets 1 like
That is, browsers are uniform (thankfully) in treating SW registrations like all other origin-controlled storage types and deciding not to do partial eviction. That is, you can't "wake up" as a SW and find your Caches are still there but not your IDB.
-
-
Replying to @slightlylate @adactio and
So joint eviction is good policy for app coherence. SW registrations aren't special in this way. That's a good thing. The correct focus here is on the *outlandish* reduction in durability for pages in a tab.
1 reply 0 retweets 1 like -
Replying to @slightlylate @adactio and
And for what? Where's the model that describes the improvements gained vs. the tradeoffs? They aren't in the post because Apple (among others) keep doing ungrounded work, e.g.: https://arxiv.org/abs/2001.07421 This is why we keep focusing on meaningful details: https://w3cping.github.io/privacy-threat-model/ …
1 reply 0 retweets 2 likes - 4 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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.