Preventing Supercookie Fingerprinting via Favicon Cache

[shampoo_factory]

Supercookie explanation and demo:
https[:]//github.com/jonasstrehle/supercookie?tab=readme-ov-file

Separate Caching Based on User Intent:

• Local Storage (Persistent):
  Store favicons on disk only if the user explicitly navigates or interacts with the page.
• In-Memory Cache (Ephemeral):
  For favicons loaded via redirects, use an in-memory cache or assign a short expiration time.
  (Note: The feasibility depends on detecting redirects reliably.)

Default Favicon Fallback:
Serve a generic favicon when none is cached, which would prevent the site from inferring a fingerprint from unique cache states.
(Note: This hand-wave-y solution may overpopulate the f-cache and cause issues with legitimate favicon rendering.)

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.