FB uses FB browser. Google uses Google browser. Spin Chrome off as standalone entity and regain moral high ground?
-
-
Replying to @chofter
: I don't care what browser people use; CCT is an open api and FB could have created it's own (drove enough traffic)
1 reply 0 retweets 0 likes -
Replying to @slightlylate @chofter
: what I care about is that users aren't being put at unreasonable risk over choices they didn't make.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @chofter
: really, this isn't hard. Choosing not to snarf navigate intents was the *default*. This is an affirmative FB choice.
3 replies 0 retweets 0 likes -
2/ instead Google Now opens web navigation intents in an in-app Chrome.
1 reply 0 retweets 0 likes -
Replying to @francip
: that's CCT; when FF implements CCT, it'll be used instead and it isn't insecure today. /cc
@chofter@alexstamos3 replies 0 retweets 0 likes -
Replying to @slightlylate
: best thing here would be a global setting that sent CCT intents to "real" navigates. /cc
@chofter@alexstamos@ade_oshineye1 reply 0 retweets 0 likes -
Replying to @slightlylate @francip and
we can’t enforce that setting. Every app developer can opt users in or out.
1 reply 0 retweets 0 likes -
Replying to @ade_oshineye
: I understand, but the libraries/frameworks people integrate could respect it. /cc
@francip@chofter@alexstamos1 reply 0 retweets 0 likes -
Replying to @slightlylate @francip and
good point. I'm convinced. Please send an email to the team mailing list about this.
1 reply 0 retweets 1 like
: doing it now.
/cc @francip @chofter @alexstamos
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.