You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see the repo is now archived and Google site says it’s no longer under consideration but I can find no announcement as to why it was dropped or what next.
The text was updated successfully, but these errors were encountered:
The Privacy Budget was found not feasible, at least right now. The proposal's objective was to set a hard limit on how much information websites could collect about users and that required solving two hard challenges: 1) Dynamically calculating the amount of information APIs are revealing about a user, 2) Enforcing a limit before a user becomes individually identifiable.
We ran testing on the proposal but couldn't find a way to implement without causing problems for both websites and users. I don't have a detailed analysis to share, but you can find an external analysis by Eric Rescorla here which I find pretty accurate about the technical difficulties. Google did publish a paper on calculating the information revealed by APIs, Assessing Web Fingerprinting Risk, for the 2024 ACM Web Conference.
I can see the repo is now archived and Google site says it’s no longer under consideration but I can find no announcement as to why it was dropped or what next.
The text was updated successfully, but these errors were encountered: