3 ms·
At the same time Apple and Google have lists of hard requirements for applications that can be extended to include these - especially if part of this change ove
by munk-a 4y ago
At the same time Apple and Google have lists of hard requirements for applications that can be extended to include these - especially if part of this change over is presenting unified shared objects for apps to use to launch browsers.
- teakettle42 4y agoThat’s true, but I still don’t believe there exists a technical solution to this problem; I think this should be solved via: (1) App Store policy, including requiring apps to disclose that they can/do capture embedded web browsing activity as part of their privacy disclosures. (2) Privacy regulation. This is a very intentional dark-pattern used to violate users’ expectation of privacy, and should be addressed. (3) User education — users should never trust an app-presented web view.
- simonw 4y agoHow about all three of yours, plus: (4) An HTTP header that websites can use to explicitly opt out of being rendered in embedded in-app browser, reinforced by App Store policy that requires apps to respect and not to work around that header
- teakettle42 4y agoThe header misleads developers and users into believing it provides security guarantees that it cannot.