Chronotope’s avatarChronotope’s Twitter Archive—№ 88,057

          1. …in reply to @eric_young_1
            ericyoung_1 jbenton dancow To be clear, the redirect methodologies between Apple and a standard bitly redirecter are significantly mechanically different in a way that disrupts how platforms like Twitter parse them.
        1. …in reply to @Chronotope
      1. …in reply to @Chronotope
        ericyoung_1 jbenton dancow You can see that a significant amount of the logic for the Apple News redirect is contained within the link's landing page and the mechanical method of redirection is substantially different and significantly non-standard.
    1. …in reply to @Chronotope
      ericyoung_1 jbenton dancow The logic for opening in the app is actually *in* the redirect page's HTML, as is the code for parsing bots, the timeout method, and the handling of failure -- problematically so! If you withdraw your content from Apple News those links *will break*
  1. …in reply to @Chronotope
    ericyoung_1 jbenton dancow And this is part of what I mean by the question of canonical-ness. The lack of publisher control of link primacy will create problems in the future. The more intermediaries between the link that faces the user and the canonical publisher link, the more threatening this issue is.


Search tweets' text