privacycg/private-click-measurement Issues

Last updated May 18, 2024, 5:49:36 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

14 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#39	Write explainer	❌	4.1 years	4 years
#40	Use more Bikeshed syntax, use Infra concepts, etc.	❌	4 years	4 years
#42	Consider using the Trust Token API for fraud prevention	❌	4 years	4 years
#45	Configurable attribution windows	❌	4 years	4 years
#58	Require both source and destination to be HTTPS / secure context	❌	3.5 years	3.4 years
#72	Support measurement of non-paid/organic clicks	❌	3.2 years	3.2 years
#73	Naming for link attribute, report fields, and well-known locations for PCM fraud prevention with unlinkable tokens	❌	3.2 years	3.2 years
#81	Blind signatures	❌	3 years	3 years
#84	Absolute final date for unsubmitted attribution reports	❌	2.9 years	2.9 years
#96	Take PCM to PATCG	❌	2.4 years	2.3 years
#97	Enable PCM measurement by a third-party on behalf of a publisher (i.e. iFrame or SFrame)	❌	2.2 years	2.2 years
#107	Per my comment in the Sept 9 call: clicks on ads are very unusual and multiple clicks are extremely rare. Given that, if a small number of tokens (say 3) was issued per request, in the majority of cases only one would be used, but in the very rare cases of multiple clicks an additional one or two could be used.	❌	1.1 years	1 year
#108	Following up on my comments on the 9/9 call.	❌	1.1 years	1 year
#111	Procurement	❌	4.8 months	4.5 months