|mediawiki/extensions/CentralNotice||master||+36 -2||Slurp and delete defunct cookies on every pageview|
|Open||None||T108849 Move CentralNotice stuff out of cookies|
|Open||None||T132640 CentralNotice: Slurp up existing wild cookies and copy them to LocalStorage or delete them|
- Mentioned In
- T131319: CentralNotice: Make a plan for moving stuff out of cookies
- Mentioned Here
- T228575: Decrease number of open tickets with assignee field set for more than two years (aka cookie licking) (March-June 2020 edition)
T135090: CentralNotice: finalize list of wild useless cookies for slurp, and push config change
T108849: Move CentralNotice stuff out of cookies
T131319: CentralNotice: Make a plan for moving stuff out of cookies
T132374: Generate a list of junk CN cookies being sent by clients
T132639: CentralNotice: Use LocalStorage instead of cookies whenever possible, for buckets, impression limiting and large banner limiting
It seems the best approach here will be to have a configuration variable with a list of old cookies to delete. We'll run through the list and remove any we find on every pageview.
The vast majority of the cookies appear to be involved in counting banner impressions. Here is a tentative list, based on Mixin parameters in logs and cookies seen on production. (See: T132374#2229057, T131319#2197176 and T108849#2050638.)
Any cookies that are expected to be reused by future or existing campaigns should be left alone, since they'll be migrated automatically to LocalStorage (by code added for T132639) when such campaigns become active.
The code that allows this is now merged. I'm making a separate task for the finalizing the list of cookies to slurp, and the related config change, since some community consultation or announcement may well be needed.
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)