Note that responsible native apps *have* a way of creating an "in app browser" that doesn't subvert user choice or break the web: https://developer.chrome.com/multidevice/android/customtabs … Any browser can implement the protocol & default browser will be used. FB can enable this with their next update.https://twitter.com/slightlylate/status/1167548118876901376 …
-
-
For most 3p content loading, that first one both runs security risks and undermines user choice. So now the choice for any referring app is up to the second two. Which is best? I don't much care. FB can easily intent out if CCT creates discomfort about attribution.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
This is...confused. FB broke the system contract by undermining link clicks and the choices users are *already making* about them. You can't start from the broken WebView-IAB-attribution-confusion counterfactual. FB broke it, they bought it.
End of 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.