You send a link, the receiving client tries to do a link preview so a request is made to the link exposing the receiver's IP address?
You send a link, the receiving client tries to do a link preview so a request is made to the link exposing the receiver's IP address?
It’s all proxies and unfurled on the server, once. Anything else is madness.
(or have one of the receiving client send it to a service out-of-band, but that "defeats" the end-to-end encryption.)
But it would be pretty bad UX if the card was just blank in these cases because the messaging server didn't have access.
Maybe this problem is intractable logically? The preview needs to be accurate from the perspective of the client. The only way to guarantee that seems to me sending the request from client.
I understood that the link in question was to some google.com, not a 'hacker' controlled URL.
[ ...Yossi sent me a link via Skype text chat to google.com. The link was to the real Google site, and not an imposter. ]
It may be something which is kept in the app's db following the generation of a preview.
Would it make sense to restrict the chats to only 'address book' contacts, supposedly trusted?