w3c/fingerprinting-guidance Issues

Last updated Dec 22, 2024, 5:53:41 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.

17 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
#33	backport minor changes	❌	5.7 years	5.7 years
#37	Best practice style change	❌	5.6 years	5.6 years
#41	Clarify "Fingerprinting mitigation levels of success"	❌	4.9 years	4.9 years
#43	should we further mitigate threats of identifiers in local storage because some mechanisms won't clear all local storage?	❌	4.6 years	4.6 years
#46	use automatic publishing	❌	4.3 years	4.2 years
#48	"Availability", not "accessibility"	❌	3.3 years	3.3 years
#54	how should we consider cumulative impacts of additions to fingerprinting surface?	❌	2.2 years	2.1 years
#55	Remove reference to browser.display.max_font	❌	1.3 years	1.3 years
#56	Concrete examples re: features for responsive design	❌	1.2 years	1.1 years
#57	broken link to Chromium documentation page	❌	5.5 months	5.2 months
#59	reconsider fuzzing and randomness as possible mitigations	❌	2.9 months	2.7 months
#60	include example of calibration and rounding as a mitigation	❌	2.9 months	2.7 months
#61	collaborative / user preference options may need to be updated (GPC rather than / as well as DNT)	❌	2.9 months	2.7 months
#62	add citations to relevant portions of Privacy Principles note/statement from TAG/PING	❌	2.9 months	2.7 months
#63	mention different forms of IP address hiding/protection	❌	2.9 months	2.7 months
#64	describe possibilities for User-Agent reduction	❌	2.9 months	2.7 months
#65	relevant research: Identified-and-Targeted / FPTrace	❌	1.7 months	1.5 months