: and let me be very clear to my friends at FB: you're hurting users & the web.
/cc @hillbrad022 @alexstamos @sebmarkbage
-
-
Replying to @slightlylate
This sentiment is not helping. Given your rubric of time spent being most important,users (or people as we call them) disagree
1 reply 0 retweets 0 likes -
Replying to @chofter
: there are secondary concerns that dominate in the medium term; security is one of those.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: using webview to load arbitrary third party content is *irresponsible*; y'all know better. /cc
@alexstamos1 reply 0 retweets 0 likes -
Replying to @slightlylate @alexstamos
FB uses FB browser. Google uses Google browser. Spin Chrome off as standalone entity and regain moral high ground?
2 replies 0 retweets 0 likes -
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
: your concern is legit & Mozilla is working on it. 'Till then, insecure browsing is unnacceptable.
/cc @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.