Signals · system · counted, not scored by the rubric
Display preferences
The colour scheme, contrast, reduced-motion and forced-colours media queries the browser reports.
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 evaluates each media query. These are user and system settings, so they follow the person more than the hardware.
Why it splits browsers apart
Dark mode splits browsers roughly in two. Reduced motion, high contrast and forced colours are rarer settings, often accessibility needs, and each one narrows the group.
What moves it
Changing the system or browser appearance settings, or a dark mode that switches at sunset.
What moving it costs
These are settings people need. Changing them to blend in costs comfort or access, and a scheme that flips with the time of day adds noise rather than hiding anything.
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 display preferences
- Can websites tell that I use dark mode?
- Yes. The prefers-color-scheme media query exists so that pages can follow your setting, and any script can read it.
- Does this site change my colour scheme?
- No. It follows your setting and offers no switch, because a site that overrides the setting would change what it records about you.
In the same group
Next
Storage quota: The storage quota the browser offers a site, rounded to whole gigabytes (or megabytes when small).
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.