Chronotope’s avatarChronotope’s Twitter Archive—№ 90,541

    1. Facebook appears to be privileging some methods of forwarding/redirect links over others. The redirects I run on Chronoto(dot)pe are no longer read as a passthrough URL on share cards (though it is in the Open Graph debugger, weird) but bitly and YOURLS methods are read as legit.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood -2 🙁
  1. …in reply to @Chronotope
    Unclear on why this is the case. Was Facebook seeing a lot of link-fraud through faking Canonical values? That seems very unlikely. No one ever reported on it as far as I can see. But then to not respect that value is... odd.
    On twitter.com Twitter logo Chronotope’s avatar Mood -10 🙁
    1. …in reply to @Chronotope
      A YOURLS redirect and my Chronoto(dot)pe redirect. Despite how it looks here, the share card for the Chronoto dot pe link shared to Facebook will have a Chronoto dot pe URL. It looks like it has way stricter methods for 'seeing' redirects.
      oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
      Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +4 🙂
      1. …in reply to @Chronotope
        Not sure if response code 200 is required, but a 301 style redirect apparently is. Notable that if your business includes 'framing' other sites this would have an impact on you as well. I'll have to play around and see what happens.
        Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +2 🙂
        1. …in reply to @Chronotope
          (In case you are curious, the reason I don't use a 301 redirect on Chronoto dot pe is so I can collect more detailed analytics.)
          Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +1 🙂

Search tweets' text