{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicdzpnozksap6xxodd6eeyhg5nydpi3gu5av3geytlam34vf2inca",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mow7zq7dsyq2"
  },
  "path": "/t/removing-client-hints-on-chromium-more-or-less-fingerprintable/38698#post_1",
  "publishedAt": "2026-06-23T00:29:58.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "By default, Chromium sends `Sec-CH-UA`, `Sec-CH-UA-Platform`, and `Sec-CH-UA-Mobile` with every request. High-entropy hints (like architecture, model, platform version, etc.) are only sent when a site includes an Accept-CH response header. (They’re also available via `NavigatorUAData` API but my concern here is specifically the request headers, since that can be blocked more easily.)\n\nDoes removing or minimizing these default Client Hints make a browser more fingerprintable (because it deviates from the expected baseline) or less fingerprintable (because it reduces entropy)? And how common is the `Accept-CH` header in the wild, actually being abused for fingerprinting in practice?",
  "title": "Removing Client Hints on Chromium, More or Less Fingerprintable?"
}