Google Messages is rethinking how link previews work, but we're not sure it's for the best

Comments

• Romkslrqusz@lemmy.zip ⁨2⁩ ⁨days⁩ ago

  TL;DR

  This beta version of the app makes it so that when you send just a URL, the recipient only sees the preview (primary image, page title, primary domain of web address)

  source

  • mustbe3to20signs@feddit.org ⁨2⁩ ⁨days⁩ ago

    It is not for the best since it is a potential security risk and questionable in terms of privacy.

    source

    • return2ozma@lemmy.world ⁨2⁩ ⁨days⁩ ago

      I hate it. I’m in the beta and it doesn’t show the full URL

      source

      • -> View More Comments
  • sem@lemmy.blahaj.zone ⁨2⁩ ⁨days⁩ ago

    Only sees a preview as opposed to a preview and the URL?

    source

    • Romkslrqusz@lemmy.zip ⁨19⁩ ⁨hours⁩ ago

      Correct

      source
    • Scolding7300@lemmy.world ⁨1⁩ ⁨day⁩ ago

      Given the other replies here: yes

      source
• _cryptagion@anarchist.nexus ⁨2⁩ ⁨days⁩ ago

  The only thing Google could do that was for the best is get hit with a meteorite large enough to wipe out the entire campus.

  source
• Nobilmantis@feddit.it ⁨2⁩ ⁨days⁩ ago

  I havent read the article nor the comments yet, but I will guess before I do: Link previews are loaded in google’s servers.

  source
• danhab99@programming.dev ⁨1⁩ ⁨day⁩ ago

  There is a metadata protocol called opengraph, it’s how apps get the information to display a rich preview. Basically the app takes the link as it’s written in the SMS message or Twitter thread and then it tries to fetch that page and then read the open graph metadata from inside. That should give it enough to show a title description and a background image, considering the web developers implemented opengraph.

  If Google is planning to use their own servers basically as a proxy then all this means is that the opengraph rich metadata is going to be a little more stale than if the app just fetch the page and generated the rich metadata itself

  source