This explains why automation fingerprints leak in ways JS shims cannot fix. Properties like navigator.hardwareConcurrency are produced by several subsystems that have to agree, and the post details what continuously rebasing a Chromium fork actually costs.
