@homakov Seems we need more than current SW to solve problems in your post. / @slightlylate @tankredhase @SakurityNetwork @bcrypt
-
-
Replying to @wanderview
@wanderview : this relates to the "old version consenting to new version" I brought up /cc@homakov@tankredhase@SakurityNetwork@bcrypt2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@wanderview@homakov@SakurityNetwork@bcrypt a dialog together with sign/verify of version w/ key continuity would be great2 replies 0 retweets 1 like -
Replying to @tankredhase
@tankredhase : I *really* don't want dialog, can built yourself w/ hooks we discussed /cc@wanderview@homakov@SakurityNetwork@bcrypt1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate Think some UA UX would be good if don't trust app itself. But yea not a dialog.@tankredhase@homakov@SakurityNetwork@bcrypt1 reply 0 retweets 1 like -
Replying to @wanderview
@wanderview@slightlylate@homakov@SakurityNetwork@bcrypt hooks are fine since the initial version of the client code is the trust anchor1 reply 0 retweets 0 likes -
Replying to @tankredhase
@tankredhase Guess I'm thinking of diff use case where user doesn't trust app on install. /@slightlylate@homakov@SakurityNetwork@bcrypt1 reply 0 retweets 0 likes -
Replying to @wanderview
@wanderview@slightlylate@homakov@SakurityNetwork@bcrypt yeah. In case of privileged api use maybe.2 replies 0 retweets 0 likes -
Replying to @tankredhase
@wanderview@slightlylate@homakov@SakurityNetwork@bcrypt but that use case is handled by browser dialogs from permissions api I guess1 reply 0 retweets 0 likes
@tankredhase : hook is tiny:
onbeforeupgrade = (e) => {
e.responses; // check
}
/cc @wanderview @homakov @SakurityNetwork @bcrypt
-
-
Replying to @slightlylate
@slightlylate@wanderview@homakov@SakurityNetwork@bcrypt the update would then be optional and triggered by the app?1 reply 0 retweets 0 likes -
Replying to @tankredhase
@tankredhase: yeah, couldn't fit it in tweet, but `respondWith` accepted/rejected promise /cc@wanderview@homakov@SakurityNetwork@bcrypt0 replies 0 retweets 0 likes
End of conversation
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.