{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibxtqcv2eezm5l4wdcgmqwo56joe6vbe5hrm4malhsvofzg3ixzei",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mmvf43keean2"
  },
  "path": "/t/ars-technica-websites-have-a-new-way-to-spy-on-visitors-analyzing-their-ssd-activity/38171#post_5",
  "publishedAt": "2026-05-28T05:06:27.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "> The technique has its limitations. First, the OPFS file must be extremely large—likely a gigabyte or more.\n\nStep one: crash the browser for 90% of people.\n\nWhile I do enjoy the validation of blocking JS by default and isolating my browsing the way I do, this also seems like a research-level issue and not a threat vector…for now.\n\nFrom the original paper:\n\n> Ultimately, the most effective mitigation would be to enable OPFS only\n>  after explicit user permission, which would significantly harm the usability of\n>  OPFS for legitimate applications and cause disruptions to user workflows.\n\nAlso seems like something that should be one day covered in browser security settings, right?\n\n…right?",
  "title": "Ars Technica: Websites have a new way to spy on visitors: analyzing their SSD activity"
}