Chronotope’s Twitter Archive—№ 154,398

This is one of the many reasons why I dislike in-app browsers so much and why any privacy-forward mobile OS should get rid of them krausefx.com/blog/ios-privacy-instagram-and-facebook-can-track-anything-you-do-on-any-website-in-their-in-app-browser
On twitter.com ♻️ 6 Retweets ❤️ 26 Favorites 2022 Aug 10 Mood -2 🙁

…in reply to @Chronotope
I have a very long history of trying to explain why in-app browsers are bad. And they are definitely bad. Chronotope/1164203656759189505
Permalink On twitter.com ♻️ 2 Retweets ❤️ 16 Favorites 2022 Aug 10 Mood -6 🙁

…in reply to @Chronotope
The right solution for in-app browsers is to get rid of them. Chronotope/1476255906975338502
Permalink On twitter.com ♻️ 2 Retweets ❤️ 13 Favorites 2022 Aug 10 Mood +1 🙂

…in reply to @Chronotope
They are undeniably unjustifiable in their existence with a very very very few exceptions (like password managers). Chronotope/1113894342467444737
Permalink On twitter.com ❤️ 6 Favorites 2022 Aug 10 Mood +2 🙂

…in reply to @Chronotope
People have absolutely done detection of in-app browsers and reacted to users leveraging them Chronotope/1007577080668749825
Permalink On twitter.com ♻️ 2 Retweets ❤️ 2 Favorites 2022 Aug 10 Mood 0

…in reply to @Chronotope
The design of mobile operating systems does push developers towards using them, even if it shouldn't. Chronotope/1121524578516336644
Permalink On twitter.com ❤️ 5 Favorites 2022 Aug 10 Mood 0

…in reply to @Chronotope
But at the end of the day I do think that treating in-app browsers differently as a developer is a viable option, one defensively protecting the open web. I really like the top article's idea to react actively to them. Chronotope/1007431618506711040
Permalink On twitter.com ♻️ 1 Retweets ❤️ 2 Favorites 2022 Aug 10 Mood +4 🙂

…in reply to @Chronotope
ericlaw/1330932882756558856
Permalink On twitter.com ♻️ 1 Retweets ❤️ 2 Favorites 2022 Aug 10 Mood 0

…in reply to @Chronotope
zachleat/1557432779339612160
Permalink On twitter.com ❤️ 2 Favorites 2022 Aug 10 Mood 0

…in reply to @Chronotope
simonw/1557426481109667843
Permalink On twitter.com ♻️ 1 Retweets ❤️ 7 Favorites 2022 Aug 10 Mood 0

…in reply to @Chronotope
A good time to reiterate that the right solution is to End the App. Apps are generally bad and we mostly don't need them. Chronotope/1288225655776215041
Permalink On twitter.com ♻️ 5 Retweets ❤️ 21 Favorites 2022 Aug 10 Mood +1 🙂

…in reply to @Chronotope
More on this slightlylate/1557861761960726529
Permalink On twitter.com 2022 Aug 11 Mood 0

…in reply to @Chronotope
Here's a really great post arguing that sites should be able to control if they are put into in-app browsers or not, in the same way they do iFrames. A strong argument, I agree, let sites choose if they want to be in-app-browsered or not... holovaty.com/writing/framebust-native-apps/
Permalink On twitter.com ❤️ 2 Favorites 2022 Aug 11 Mood +7 🙂

…in reply to @Chronotope
The right answer is to get rid of them entirely, but if not that then this is a step in the right direction.
Permalink On twitter.com ❤️ 2 Favorites 2022 Aug 11 Mood 0

Search tweets' text