Talk:Reading/Web/Preference Persistence For Anonymous Users/Prototype Summary

Safety: deanonymization
One of the biggest risks that this feature should guard against is to prevent accidental deanonymization of unregistered readers. Sending a unique or unusual combination of client preferences back to the server will increase this risk, please address this issue in the "safety and security" considerations. I've seen the proposed design for this feature wavering between localstorage and cookies, but the current implementation seems to suggest an uncritical choice of cookies. Is this still the case?

"The patch utilises cookies for storing client preferences, as it is easier to monitor on production systems"

Adamw (talk) 07:30, 22 August 2023 (UTC)