3 ms·
Weirdly, this is something that Apple actually gets right - the little „previews” you get when sharing links in iMessage get generated client-side; _by the send
by klausa 1y ago
Weirdly, this is something that Apple actually gets right - the little „previews” you get when sharing links in iMessage get generated client-side; _by the sender_.
There are good reasons why you’d not want to rely on clients providing this information when posting to LinkedIn (scams, phishing, etc); but it’s interesting to see an entirely different approach to the problem used here.
- pmontra 1y agoI came here to write that I expected that clients should generate previews after receiving a link inside a message. I also expected that somebody else would have already pointed that out and here we are. However I also understand that there are a number of reasons for a server to scrape the link. In no particular order: 1. scraping all the things, they might be useful sometimes in the future. 2. the page changes, goes 404, the client is reset and loses its db and can't rebuild the preview, but the client can rely on the server for that 3. it's faster for the client as the preview comes with the message and it does not have to issue some extra calls and parse a possibly slow page. Anyway you write that's the sender that generates the preview on iMessages so that's leaves point #1 and possibly the part of #2 about flaky internet connections: the server is in a better place to keep trying to generate the preview.