Finally had a chance to write up some thoughts about last week's discussion with @adactio: https://infrequently.org/2016/05/not-the-post-i-wanted-to-be-writing/ …
/cc @jaffathecake @phae
-
-
Replying to @slightlylate @adactio and
I left a comment. You should have included the security aspect of URL accessibility.
2 replies 0 retweets 0 likes -
Replying to @Paul__Walsh @slightlylate
can you describe how security is lost in the current model?
1 reply 0 retweets 0 likes -
Replying to @jaffathecake @slightlylate
You mean, by not being able to see the URL, what are the security implications?
2 replies 0 retweets 0 likes -
Replying to @Paul__Walsh @slightlylate
well, you need to consider the whole thing, like how you get into the situation of no visible url.
3 replies 0 retweets 0 likes
Replying to @jaffathecake
: right. The PWA "install" step is basically the capability to run fullscreen for the origin in question.
4:11 PM - 31 May 2016
1 reply
0 retweets
1 like
-
-
Replying to @slightlylate @jaffathecake
: and if any of those properties are degraded, we bounce you back to browser or show security indicator (w/ URL)
1 reply 0 retweets 1 like - 12 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.