Charlie Harrison

This seems like a pretty reasonable default behavior to me. Let's bring this up in the next call to see if others agree. cc @johnivdel

@alois-bissuel thank you for filing. This is the intended behavior of the priority system and I agree it is not perfect for all scenarios. We introduced it to allow for...

> I am not sure I follow the second solution. Isn't it the very role of priorities for dropping conversion in the queue? Yes, but the existing proposal is heavy...

We discussed this in the meeting today (will post the minutes shortly). My takeaway from the conversion was: 1. @johnivdel mentions that the [dedupe key functionality](https://github.com/WICG/conversion-measurement-api/blob/main/event_attribution_reporting_clicks.md#:~:text=the%20same%20source.-,dedup%2Dkey,-%3A%20optional%20signed%2064) could be used to...

For an MPC system the threat model should include a helper acting maliciously. Otherwise, the reasons for doing MPC are less clear in the first place. I think it makes...

We chose this by following the advice in https://w3ctag.github.io/design-principles/#milliseconds. I'm OK with something more ergonomic but I think we should consider filing a bug on TAG if the advice is...

@apasel422 good point. I don't know if it strictly applies, but it felt like the logic generally applies across all web platform APIs: > Even if seconds (or some other...

It looks like milliseconds might not have been the right choice. Especially now that we may be moving to response-based registration we should try to match other header-based APIs for...

Thanks for filing! We moved from origin-based attribution scoping on the destination to eTLD+1-scoped attribution to allow for landing pages and conversion pages to be on separate origins. This helps...

Thanks for filing John. We are experimenting with a more complicated set-up that is simpler than full multi-touch but more complex than last-touch: one that allows each source event to...