Signals · rendering · counted, not scored by the rubric
Emoji rendering
A hash of how this browser draws a set of emoji: their sizes and pixels with the system emoji font.
Rubric 1.0.0 does not print a prior for this value. The population still compares it, so the box beside this text counts how many of the devices these sites have read share yours.
How a page reads it
The collector draws a fixed set of emoji and hashes what came out. The emoji font belongs to the operating system, so the result follows the system, not the browser.
Why it splits browsers apart
Every operating system release ships its own emoji set, and new emoji render as boxes on older systems. The hash therefore splits devices by system and system version.
What moves it
An operating system update that ships new emoji, or installing a different emoji font.
What moving it costs
A user agent claiming Windows while the emoji render with the Apple set is a contradiction a page can see in pixels.
How the count is made
Your value is compared with the latest reading of every device the eight sites read in the last 365 days, this browser's own rows left out. The share is (devices sharing it + 1) ÷ (population + 1), and the bits are −log₂ of that. Why the counts sit beside the priors and are never added to them.
Questions about emoji rendering
- Why would emoji identify my device?
- The emoji font comes with the operating system and changes with its versions. Drawing a few emoji shows which system and which release drew them.
- Does it stay the same after a browser update?
- Usually, because the font belongs to the system, which is why this value is part of the device key.
In the same group
Next
Maths engine: A hash of the exact results of a set of maths functions such as Math.tan, Math.exp and Math.sinh for fixed inputs.
Where the pens move
A value patched in the page is a patched value. Set in the engine, it is just a value.
Engine level, not JS level. Donut Browser spoofs through CDP injection in its Wayfern Chromium fork, so the value a page reads is the value the engine reports — there is no patched accessor to catch.
It refuses to contradict itself. A profile whose proxy exit geography, time zone or language disagrees with its fingerprint does not launch. That is a pre-launch gate in the app, not advice in a manual.
Open, and quiet. AGPL-3.0, desktop app and sync server both in the repository, and no analytics SDK anywhere in the source. macOS, Windows, Linux.