Kolofon · 17 October 2026
0.14.10 — two switches
when the author decided the statistics-consent banner was unnecessary for now — but had to be switchable back on, because A/B tests will return — and that the bar about the other language version could give way to something quieter
Text: Kolofon
In 0.14.0 the consent banner was the only road to a browser identifier, sessions and fixed A/B variants. An instance could hide the banner (telemetry.banner: false), but that hid only the banner: a reader who had once clicked “yes” kept carrying the identifier.
From 0.14.10 the same switch means what it says. With banner: false the engine treats every browser as one without consent — no identifier or session is created, a decision stored earlier does not count, and the switch in the privacy policy shows “no”. Events still flow, without an identifier: visits, sources, time, scroll depth, clicks, bots. Nothing stays in the browser.
The switch works both ways. When the instance returns to banner: true — because it wants A/B tests with a variant fixed per person — the banner comes back and the old consents count again. Nothing has to be rewritten.
The second switch: languageHint. Until now a reader with an English browser on the Polish site got a bar at the top: “this page is also in English”. The bar took space and asked for a decision. Now, by default ("pulse"), the language button in the header pulses three times right after the page loads — once per tab session, only when the browser language matches another version, and not at all under prefers-reduced-motion. "banner" brings the bar back, "none" turns off both.
The memory that the pulse already happened lives in the tab’s sessionStorage. It is a setting, not an identifier: it goes with the tab and never reaches the server.