Hacker GitHub

← All repos

mikewest/privacy-budget

View on GitHub ↗ ★ 208 archived

14 mentions on Hacker News by 9 people: 0 stories, 14 comments · first 2019-08-22 · latest 2025-11-23

Mentions per year 14 mentions · busiest year 2020 (4)
20082026
  1. …on AI instead of privacy. [0]: https://privacysandbox.com/news/privacy-sandbox-next-steps/ [1]: https://github.com/mikewest/privacy-budget [2]: https://mozilla.github.io/ppa-docs/privacy-budget.pdf [3]:…
  2. …is preventing browser fingerprinting by limiting informational entropy from user environment. https://github.com/mikewest/privacy-budget
  3. …if it supports granular per-site control, which may be needed for certain specialized websites. https://github.com/mikewest/privacy-budget
  4. …what information, and eventually browsers can start enforcing something like privacy budgets ( https://github.com/mikewest/privacy-budget ). You can't do these with something always sent automatically.
    comment by jefftk · 2022-11-05 · in User-Agent Reduction
  5. …from the same issues. [0] https://www.chromium.org/Home/chromium-privacy/privacy-sandb... [1] https://github.com/bslassey/privacy-budget
    comment by ehsankia · 2021-04-21 · in Everybody Hates “FLoC”
  6. …surface gets a score and each origin has a budget. Once you go over, something(?) happens. https://github.com/bslassey/privacy-budget
  7. …which is now called privacy budget. https://blog.chromium.org/2020/01/building-more-private-web-... https://github.com/bslassey/privacy-budget
  8. Switching it from passive to active means you can count it towards https://github.com/bslassey/privacy-budget . Yes, sites can ask for all sorts of things, but if they ask for enough that they could plausibly be fingerprinting you then…
  9. …to switch from passive methods to active methods means you can apply a privacy budget: https://github.com/bslassey/privacy-budget Then sites that need some information can get it, but won't be allowed to get so much identifying information…
    comment by jefftk · 2020-01-26 · in Am I Unique?
  10. This is part of what the Privacy Budget ( https://github.com/bslassey/privacy-budget ) proposal aims to tackle. Freezing the User-Agent string reduces the amount of information exposed by default. UA Client Hints means the site has to…
  11. It changes the passive fingerprinting vector to an active one: https://github.com/bslassey/privacy-budget#passive-surfaces So, while UA hints could potentially supply more information than the current UA string - each item needs to be…
  12. …seems rather promising. [1]: https://bugs.chromium.org/p/chromium/issues/list?q=component... [2]: https://github.com/bslassey/privacy-budget
  13. …more intrusive ones. [1]: https://blog.chromium.org/2019/05/improving-privacy-and-secu... [2]: https://github.com/bslassey/privacy-budget
  14. …flocks of sensitive categories, but pretty sure the default isn't going to be random. -- > https://github.com/bslassey/privacy-budget > Fundamentally, we want to limit how much information about individual users is exposed to sites so that…