3 ms·
Nah. +-------+ +----------------+ +------------+ |Browser|<==A==>| Visited server |<==B==>| ID service | +-------+ +-------------
by pygy_ 14y ago
Nah.
+-------+ +----------------+ +------------+
|Browser|<==A==>| Visited server |<==B==>| ID service |
+-------+ +----------------+ +------------+
The client data acquisition is done through A (AJAX), then that info is sent through B (API call) to get the identity. The browser doesn't interact directly with the ID service.
The data acquisition scripts would be served directly by the web sites.
- andrewcooke 14y agodid you read the article? they explicitly say it's implemented in the browser with "tracking code". you can certainly make something that is "ghostery proof", but (1) this isn't it and (2) it would be more complex to deploy and so gain less traction.
- pygy_ 14y agoI read the article, and you didn't get my post. It wasn't about this very company, but tracking in general, which can be implemented without serving code from a third party server. If solutions like Ghostery become the norm, there are still workarounds, and they will catch up if nothing else works.