Why this topic matters to me now
The OS token in User-Agent is too convenient to trust. GPU strings, voices, pointer/hover, capability APIs — these are public signals of device form. I deliberately do not idolize UA-OS.
Public tools already show another path: build a “surface portrait” that resembles an OS class, without worshipping a string. I phrase the conclusion carefully: “the surface looks like…”, not “the hardware is proven”.
Public frame (links)
I look at the x-bot Chrome API + OS Detector approach, at Apple alternative browser engines (the EU breaks the old “iOS ⇒ WebKit everywhere”), and at the Client Hints docs. Together they kill the naive equality UA-OS ≡ reality.
What I observe in the lab, in plain words
A multi-signal portrait
The idea is not one magic API, but an ensemble of surface expectations. An ensemble lies more softly than a single token — and more honestly admits uncertainty. That is the same philosophy as “consistency beats one hash”, applied to OS class.
Traps
Emulation. Cut-down speech and sensor subsystems. Corporate policies. Alternative engines on iOS in the EU. Any of these makes the phrase “proven OS” arrogant.
The EU shift is especially treacherous: old rules like “on iOS there is always one engine” stop being a law of nature. If my lab brain still lives in 2019, I will be wrong loudly and confidently.
Honest language
“Looks like an Android-class surface” — fine. “This is exactly a specific model with such-and-such drivers” — already another genre, and often a lie. The diary must distinguish these phrases.
What this changes in detect and/or in the build (without specifics)
Detect learns not to scream “OS spoof” on every rare stack. The build learns not to treat matching one token as a win when the surface has drifted apart.
When I change the research contour, the question is not “did UA-OS match”, but “did the surface class stay consistent across several rooms”.
What I will not say and why
No internal signatures, no guide “how to become iOS in the logs”, no recipes for a specific antifraud stack.
Short first-person takeaway
For me, OS is a hypothesis about surface class. UA may hint. The surface may support or refute it. In this series I do not “prove” the hardware.
