Augur.io如何实现跨浏览器的设备唯一识别？
Great question! Let’s break down how Augur pulls off device-level unique identification across different browsers, and why it struggles to generate that ID in Safari on Mac.
The fact that augur.json.consumer.UID stays the same across all browsers on a single device tells us Augur isn’t relying on standard browser fingerprinting (which is tied to specific browser attributes like user agent or canvas rendering). Instead, it’s tapping into system-level mechanisms that span all browsers:
OS-native unique identifiers: Most operating systems have a built-in, device-specific ID that persists even across OS reinstalls—think Windows’ Machine GUID or macOS’s Hardware UUID. Augur probably uses a specialized helper (like a lightweight desktop app, native messaging host, or browser extension) to fetch this OS-level ID and make it available to the browser script. Since this ID is tied to the device itself, not the browser, it’s consistent across Chrome, Firefox, Edge, etc.
Cross-browser shared storage: While standard browser storage (localStorage, sessionStorage) is locked to each browser, Augur might write a unique ID file to a system-wide accessible location—like a public user folder on Windows or a shared directory on macOS. If the browser has permission to read this file (via file system access APIs or that same helper tool), it can pull the same ID no matter which browser you’re using.
Hardware-based identifiers: Some devices expose unique hardware attributes (like motherboard serial numbers or disk drive IDs). Again, this would require a privileged helper to access these low-level details (since browsers don’t natively expose them for privacy reasons) and pass the ID to Augur’s script.
Safari’s aggressive privacy protections make it much harder for tools like Augur to access system-level data. Here’s the breakdown:
Strict sandboxing & tracking prevention: Safari’s Intelligent Tracking Prevention (ITP) blocks cross-site tracking and restricts access to non-browser-native storage or APIs. It actively limits scripts from interacting with system files or tools that could expose device identifiers.
Tight macOS security controls: Safari runs in a strict sandbox that prevents it from accessing system files, hardware details, or communicating with unapproved native helpers. Unlike Chrome or Firefox (which allow more flexible extensions and native messaging), Safari’s extension ecosystem is heavily restricted—making it nearly impossible for Augur to fetch that system-level ID.
Anti-fingerprinting safeguards: Safari actively blocks or randomizes many attributes used for fingerprinting, and it extends these protections to block access to device-level identifiers that could be used for persistent tracking.
内容的提问来源于stack exchange，提问作者Meraj Ahmed
