{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigz3xismwkqkb7jm2ivpcjzfrmo673gs2oj4qvpbvi7iiwvvvx3cm",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mkbl6zuaj2u2"
  },
  "path": "/t/randomizing-browser-figerprint-good-practice/37404#post_7",
  "publishedAt": "2026-04-24T21:00:19.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "anon9274927:\n\n> which means every time I will reload a page **I will get a new fingerprint** that way those big tech survaillance companies won’t be able to **track me**\n\nPrima facie: fine. That’s one way of doing it. But are you making yourself _too unique_ in the way you interact _on that page_. I guess, if your threat model is the tracking across _pages_ , then fine. But then I don’t know how **new** this fingerprint is.\n\nIf, what you describe, is your threat model ‘as is’ then you’re doing a good job. If you’re talking ISP, packets and whatnot (and much, much more…), then no.\n\nSo: good job!",
  "title": "randomizing browser figerprint good practice?"
}