Chronotope’s avatarChronotope’s Twitter Archive—№ 154,412

                    1. 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
                      OpenGraph image for krausefx.com/blog/ios-privacy-instagram-and-facebook-can-track-anything-you-do-on-any-website-in-their-in-app-browser
                  1. …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
                1. …in reply to @Chronotope
                  The right solution for in-app browsers is to get rid of them. Chronotope/1476255906975338502
              1. …in reply to @Chronotope
                They are undeniably unjustifiable in their existence with a very very very few exceptions (like password managers). Chronotope/1113894342467444737
            1. …in reply to @Chronotope
              People have absolutely done detection of in-app browsers and reacted to users leveraging them Chronotope/1007577080668749825
          1. …in reply to @Chronotope
            The design of mobile operating systems does push developers towards using them, even if it shouldn't. Chronotope/1121524578516336644
        1. …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
      1. …in reply to @Chronotope
    1. …in reply to @Chronotope
  1. …in reply to @Chronotope
    1. …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
      1. …in reply to @Chronotope
        1. …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/
          OpenGraph image for holovaty.com/writing/framebust-native-apps/
          1. …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.


Search tweets' text