Rubric 1.0.0 · column 7 of 13
Time zone
The IANA zone the Intl API resolves to, such as Europe/Berlin. Not the UTC offset — the zone identifier.
Under rubric 1.0.0 this column is worth between 4.32 and 7.38 bits, and the likeliest outcome the table knows — America/New_York — costs 4.32. Those figures are assumptions printed before your run. The counted box beside them is not: it is how many of the devices these sites have read share your value.
How a browser produces a time zone
The browser asks the ICU internationalisation data bundled with it to resolve the operating system clock setting into an IANA zone identifier, and hands the page a string like Europe/Amsterdam. That string is far more specific than a UTC offset: America/New_York and America/Toronto share every offset they will ever have and are different values here. It is also stable, cheap to read, and requires no permission, which is why it is one of the first things every consistency check compares against an exit IP.
How rubric 1.0.0 prices a time zone
Two buckets and nothing in between. Twelve named zones — New York, London, Berlin, Paris, Los Angeles, Chicago, Shanghai, Kolkata, Tokyo, Moscow, Sao Paulo and Amsterdam — share an assumed 0.05 and cost 4.32 bits each. Every other zone on earth shares 0.006 and costs 7.38 bits. There is no third tier, so Europe/Dublin and Pacific/Chatham are priced identically despite being nothing alike.
The spread between the cheapest and the dearest outcome is 3.06 bits, and that spread is the whole of what this column can ever do to a total. Where the four band edges sit →
Every outcome this rule can produce
This is the printed envelope, written out. The pen cannot land outside it, because these are
all the answers rule timezone has.
| Outcome | Assumed p | −log₂p |
|---|---|---|
| America/New_York any of the twelve busy zones modal outcome — the printed line | 0.050 | 4.32 |
| Pacific/Chatham any zone outside them | 0.0060 | 7.38 |
What changing a time zone costs
Moving from a tail zone into one of the twelve saves 3.06 raw bits, and time zone is grouped with language preferences so you may keep only 35% of that. The real cost is elsewhere: the zone is the signal most often compared against the exit IP of a proxy, and a Frankfurt exit reporting America/New_York is a mismatch that no bit count on this form prices. Changing the zone without changing the exit is a strictly worse position than the one you started in.
The rubric's own reasoning, verbatim
There are hundreds of IANA zones but traffic concentrates in a few dozen. Assumed uniform-ish across the busy zones with a long tail.
What moves it
The system clock setting, or a browser that overrides it to match a proxy exit. Overriding it without matching the proxy exit produces a contradiction, which is a worse outcome than a rare zone.
Where this prior is weakest
Twelve zones share one prior of 0.05 and every other zone on earth shares 0.006. Asia/Kolkata and Europe/Amsterdam do not carry remotely the same traffic, and pretending they do is the least defensible simplification in this table.
Correlation
Grouped with Language preferences under "locale". Whichever of them carries the most surprisal in a given pass takes full weight; the others take 35%. The chart draws the short stroke rather than describing it.
How the correlation discount works →
Challenge it
If you have a source that contradicts this assumption, the honest thing is to say so in
public against this specific prior. Open a challenge
against timezone →
What people ask about a time zone
Answered from rubric 1.0.0 itself. Where an answer quotes a probability, that probability is a constant in the shipped scoring code and is printed in the table above.
- Why is my time zone worth more than my operating system?
- Because the rule assumes zones outside its list of twelve are rare, at 0.006, while Windows is assumed at 0.62. A tail zone costs 7.38 bits and Windows costs 0.69. Both figures are assumptions printed before your run.
- Does the rubric read my UTC offset or my zone name?
- The zone identifier, resolved through the browser internationalisation data. Two zones that share an offset all year are still different values here, which is why the identifier is a stronger signal than the offset.
- Should I match my time zone to my proxy exit?
- Matching is the point. This form scores rarity and cannot see the mismatch at all, but a time zone that disagrees with the exit country of your proxy is the contradiction that consistency checks look for first.
Where to read next
- The prior for language preferences — the other reading the locale group discounts this one against.
- The complete prior table for all 13 columns — every rule, every outcome, and the rationale the rubric ships with each one.
- Assumed and counted: what a prior is, what the counted column beside it measures, and why the two are never added.
- Compare two passes for the delta on this column — change one setting and read what actually moved, instead of guessing from a total.
Where the pens move
Knowing which prior is weak is only useful if something can actually move the signal.
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.