{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieb4qizi35g2kys7t2xkllz4w5pbyat4b6mocukytgbl7t5wyojgq",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3ml6x4g2tscf2"
  },
  "path": "/t/hister-a-free-self-hosted-personal-search-engine/37668#post_19",
  "publishedAt": "2026-05-06T14:32:52.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "https://amiunique.org/"
  ],
  "textContent": "asciimoo:\n\n> Yes, this is where the problem lies. Using random UUIDs makes the extension fingerprinting impossible, but it makes the browser fingerprinting fully possible even without cookies. Nice that the websites can’t query what extensions you use, but by the fully unique extension ID they can identify your browser any time. I think it is a much bigger privacy risk.\n\nI stand corrected. I thought they would reset on browser restart but it seems like they persist (per profile).\n\nasciimoo:\n\n> How can servers get information about your extensions without using javascript?\n\nThe browser still transmit a load of metadata and other information. Not using JS also makes you stand out a lot. If you open https://amiunique.org/ for example in a Tor Browser without JS enabled you can still see quite a bit.",
  "title": "Hister: A free & self-hosted personal search engine"
}