[newsignup]

> The GIPHY service could use subtleties like TLS session resume or cache hits to try to correlate multiple requests as having come from the same client, even if they don't know the origin.

How would a cache hit mean same user tried to search? TLS session resume, I can understand but cache hit only means same resource was accessed not same user tried to access.

[StavrosK]

You cache a unique ID and then see if you get a hit.

[newsignup]

Which unique id? I thought the point of sending it via Signal was to not include any user id or any other id.

[detaro]

Presumably the clients cache GIFs, maybe even search results, instead of re-fetching them every single time.