I have been an EMParrot user for some time. I use it for managing the email for my extended family. I have dozens of cousins, so EMParrot has been a great way to manage all the communications traffic. With this long list of participants, sending email used to be a challenge, with changing addresses, new members and the occasional user getting hacked and spamming everyone. Now, with the ability to contact anyone 1-on-1 through EMParrot, we can send personal messages without having to find specific addresses and without the worry of corrupt messages. I recommend EMParrot to anyone who has a long list of people to connect.
What 1,500 Emails Reveal About Tracking
The earlier posts on this blog – The Cookie That Never Expires and UID2: The Standard That Replaced the Cookie – made an argument about how the ad industry replaced the cookie with your email address. This post is not an argument. It is what happened when that argument got pointed at one person’s actual mail.
The corpus is two personal mailboxes, a handful of single-service aliases, and a script that never once touches the network – it only reads what senders already embedded in the message. What came back is a specific, traceable answer to the industry’s favorite defense, that tracking pixels are harmless aggregate telemetry counting opens. The mail says otherwise, and it says something stranger besides.
