ephemeral fingerprinting
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
At first glance, I'm not clear on whether events can be fired based only on context-dependent timers or also based on external things. If the latter, then presumable service workers could be a vector for ephemeral fingerprinting. Even if there's not an issue, this should be written up in the privacy considerations section, providing justification for why it's not an issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the privacy considerations section and the issue's question about context-dependent timers and external triggers. Determine whether service workers enable ephemeral fingerprinting through external events, then document the conclusion and its justification in that section; no specific file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100