ipa

It's all other parties, actually. I'm assuming Mozilla and friends are trusted and that the cryptography is perfect. I've filed an issue at https://github.com/patcg-individual-drafts/ipa/issues/90 but I'm still not sure if that's the right repo.

Does MPC, which PPA uses, use attestation? I'm under the impression it doesn't (at least currently): https://github.com/patcg-individual-drafts/ipa/issues/22

Technical docs are here: https://github.com/patcg-individual-drafts/ipa/blob/main/IPA... Might be worth opening an issue if you believe there's merit to the attack?

> you don't need to worry that toggle will get mysteriously turn back on. I will be caustious with such statement. https://github.com/patcg-individual-drafts/ipa/ IPA now allows these companies to track users across multiple IP addresses, and regardless of the user's cookie settings, via a unique tracking identifier. It is also proposed that the operating system provides the unique tracking identifier which can then be used by all applications or browsers on a device, allowing different devices behind a single IP address to be distinguished. Mozilla is one of the authors.

Can Mozilla also respond with their position on their own IPA proposal[1] for tracking users across the Internet? If you are shown a product ad whilst browsing searchengine.example and then later look up the product at reviews.example, then end up making a purchase at shop.example, your Mozilla browser will send all of these events to one or more aggregation services that allows shop.example to understand (at least in aggregate, assuming you trust the cartels running the aggregation services) that you were exposed to their product at searchengine.example and further exposed to their product at reviews.example. Where previously an ad tech company was ultimately able to track users based on source IP address (even if cookies had been disabled by a user), IPA now allows these companies to track users across multiple IP addresses, and regardl

Mozilla are proposing IPA[1] which is designed to track user interaction with ads and product marketing, and track any conversion that occurs (e.g. users end up purchasing something). If you are shown a product ad whilst browsing searchengine.example and then later look up the product at reviews.example, then end up making a purchase at shop.example, your browser sends all of these events to an aggregation service that allows shop.example to understand (at least in aggregate, assuming you trust the cartel running the aggregation service) that you were exposed to their product at searchengine.example and further exposed to their product at reviews.example. [1] https://github.com/patcg-individual-drafts/ipa/