3 ms·

That annoyance may be enough to keep many actors from just plugging 10 random trackers into their sites, especially when it means running code from less-than-tr

That annoyance may be enough to keep many actors from just plugging 10 random trackers into their sites, especially when it means running code from less-than-trust-worthy parties on their own servers instead of their user machines. At the very minimum it aligns incentives better for developers to think about these things. And with IPv6 privacy extensions IP addresses will also be less useful for server-side tracking.

auslander 7y ago
> especially when it means running code from less-than-trust-worthy parties on their own servers instead of their user machines. But most will be OK with their servers running Google, Amazon, Oracle BlueKai and Facebook code, the scariest ones by amount of data.
yyyk 7y ago
"IPv6 privacy extensions...." I recall these extensions are just optional. How many implementations actually implement these extensions? I recall Windows 10 had this broken for a year and almost nobody noticed...
- the8472 7y ago
  They were broken in the sense that the preferred address would revert back to the permanent address. IPv6 still worked.
  - yyyk 7y ago
    If the address reverts to the permanent address, than the IP can still be useful for tracking, right?
    - the8472 7y ago
      Yes, that was the issue that was fixed.
sciurus 7y ago
They didn't have to run the code, e.g. example.com just has to run a proxy that accepts payloads at analytics.example.com and forwards them to the third party tracking providers.