-
FB is going to ship its own chromium engine to power their IAB instead of using the system-provided webview. None of this solves the problem where the FB "browser" doesn't bring your privacy / security settings, sessions, passwords, etc. x.com/tomayac/status/1575943083732058112Permalink On twitter.com
♻️ 15 Retweets ❤️ 35 Favorites Mood -1 🙁
-
It's also perfect timing as the teams building these webviews are looking into ways to block FB's IAB if the site requests it, and open the page in the user's preferred, default browser. FB would have no control over that.Permalink On twitter.com
-
By shipping their own engine, they can opt-out of this behaviour, ignore the site's request, and keep spying on the user.Permalink On twitter.com
-
FB also mentions "stability" as an important reason for shipping their own engine. Apparently, apps that embed webviews crash when the underlying WebView app is updated. AFAIK, this would not be an issue if FB would just use CCT instead of a WebView. 9to5google.com/2022/09/30/facebook-android-webview/Permalink On twitter.com
-
Maybe more importantly, FB is pretending to be a browser without making it absolutely clear that they are asking for a LOT of trust. webventures.rejh.nl/blog/2022/in-app-browsers-are-tracking-you/On twitter.com
