Charlie Harrison

Thanks for the response and clarification. I actually think the problem in (1) and (2) is worse than you say, because in lots of cases in the display advertising world,...

Yes I think this is possible. Here are some quick and dirty ideas: 1. Do this with some HTTP-only hooks. We'd need to think through the design but you could...

I thought about this a bit more the other day and I think you can sign the conversion metadata in a way to prevent upgrade attacks. In the trust token...

Thanks, I am familiar with the proposal. The problem with using public metadata (i.e. 8 different key pairs) is that it is difficult to integrate with noise as I mentioned...

Hey @k-o-ta , can you explain how you would propose the agg service: 1. Scales different contributions with different values of `scalingFactor`? 2. Applies noise when different contributions have different...

Thanks for tagging me. I am excited to see this proposal progress. On the last web perf call there was some mention of making this extensible to multiple data types...

+1 to including the epsilon value (or some rate of flipping) in the API itself. This provides a few benefits: - Different browsers can choose more or less strict values...

@mwjacksonmsft thanks. One other question: let's say we expand this interface to support more data types - would we expect some users to still prefer a higher accuracy single `confidence`...

@mwjacksonmsft I think the primary factor is just dealing with a breaking change. E.g. if we move from randomized response to RAPPOR, everyone will need to update their code to...

There is a spectrum of breakage: 1. The flip probability of `confidence` changes. This is a small issue but resolvable by downstream systems with maybe a single line of code...