Turan 1.0 release notes

1.0 is the first version we are comfortable recommending to someone who does not want to think about settings. It is also the version where we removed things.

Added

• Preset groups. The grid is now grouped by intent — eye care, contrast, glass, blob, dark — instead of one flat list sorted by internal id. The old ordering only made sense to us.
• Per-site rules. Turn Turan off (or pin a specific preset) for one hostname. Rules match the hostname exactly, so docs.example.com and example.com are independent.
• Per-preset intensity. Intensity used to be global, which meant switching from a warm preset at 30% to a dark preset at 95% required two slider trips every time.
• Sync across devices. Presets, intensity and site rules sync through your Turan account. Off by default, and it stays off until you sign in — nothing is uploaded by installing the extension.

Changed

• Intensity is per-preset now. If you had a global intensity of 50%, every preset starts at 50% after the upgrade; your old value is not lost, it is just copied to each preset once.
• Site rules match hostname only. 0.9 matched by registrable domain in some builds, so disabling a broken docs.example.com also disabled example.com. Rules created before the upgrade are kept, but they will apply to exactly one hostname from now on. If a site behaved differently than expected after upgrading, this is the first thing to check.

Removed

• The Apply button. Every change is live and reversible.
• The account requirement for presets. Free presets never needed an account and no longer even hint at one.
• The Chrome Web Store "manage data" prompt. Read the privacy policy for exactly what is and is not collected.

Deliberately not shipped

• Automatic per-site detection of "bad" hosts. We tried a heuristic that flagged pages where a colour layer failed to cover the background. It produced false positives on roughly one in five sites, which means turning the extension off for pages that were fine. The manual switch stays.
• A custom CSS box. It is the most-requested feature and the one we are least likely to ship: arbitrary CSS from a synced account is remote code execution with extra steps.

Upgrading

The extension updates itself through the store. If presets look wrong immediately after the update, reload open tabs once — pages loaded under the previous version keep the old injected layer until they reload.