{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibrxopv3flpjgt6sdv4rmpatibppsah6zajo3gelhrjsxz4m7hpnu",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3me7t6hhc6fe2"
  },
  "path": "/t/will-brave-debloating-by-changing-registry-values-create-a-new-attack-surface/35234#post_4",
  "publishedAt": "2026-02-06T20:35:43.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "github.com",
    "GitHub - RKNF404/chromium-hardening-guide: Harden chromium (somewhat)"
  ],
  "textContent": "Honestly, most of those simply remove bloat and can be configured within the browser to the same effect. You certainly won’t be increasing your attack surface though.\n\nFor more thorough browser policies I recommend:\n\ngithub.com\n\n### GitHub - RKNF404/chromium-hardening-guide: Harden chromium (somewhat)\n\nHarden chromium (somewhat)",
  "title": "Will brave debloating by changing registry values create a new attack surface?"
}