2 ms·
It does, and as usual, Apple catched up a decade later. It was called Google Image Proxy for GMail (or something like that) when it was released, much to the ch
by ASalazarMX 1y ago
It does, and as usual, Apple catched up a decade later. It was called Google Image Proxy for GMail (or something like that) when it was released, much to the chagrin of email marketers.
One of the earliest (2013) mentions I could find:
https://gmail.googleblog.com/2013/12/images-now-showing.html https://gmail.googleblog.com/2013/12/images-now-showing.html
Found in this old article about the initial launch: https://words.filippo.io/how-the-new-gmail-image-proxy-works-and-what-this-means-for-you/ https://words.filippo.io/how-the-new-gmail-image-proxy-works...
- Barbing 1y agoThank you. So, important difference! Since 2013, marketers haven’t known WHERE their readers are simply from users opening an email in Gmail. But today, marketers don’t know IF their readers even open an email if users use Apple Mail. Partial quote from the second article: “The issue is that the single most useful piece of information a sender gets from you[/the proxy] loading the image is that/when you read the email. And this is not mitigated at all by this system [b/c] when you open an email the server will see a request. Mix that with the ubiquitous uniquely-named images … and you get read notifications.” (I want _neither_ to leak my IP _nor_ to have “Read Receipts” enabled when I get spam or whatever.)