Page MenuHomePhabricator

CentralNotice: finalize list of wild useless cookies for slurp, and push config change
Open, Needs TriagePublic2 Estimated Story Points


CentralNotice code to slurp up useless, old, wild cookies has merged and is awaiting deployment.

After that, we'll need to put a list of old cookies for slurp in mediawiki configuration, via $wgCentralNoticeCookiesToDelete.

Here is a list of cookies to cull. We should finalize the list... What sort of community outreach do we need for this? What sort of announcements? I think at least we'll want to check that none are for currently active campaigns...

Event Timeline

Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptMay 12 2016, 1:36 AM
DStrine assigned this task to AndyRussG.Jul 26 2016, 8:18 PM
Ejegg added a subscriber: Ejegg.Feb 15 2018, 12:42 AM

Aha, so this is the task you meant when you said 'we should use that cookie deleting code'.

I wonder how many cookies there are left... We've had localStorage as a requirement for serving JS at all since April of 2016:

So we should always be using localStorage instead of cookies, even for the [Ff]undraising category.

This should totally be added to the current sprint. How can we have a dinosaur cookies sprint & not include this one

Ejegg added a comment.Feb 15 2018, 4:29 PM

@AndyRussG do you have the queries handy that you used to make that list so we could refresh it?
@Jseddon would you have some time in the next couple weeks to ask other CentralNotice users about the cookies that they might care about?

I'm feeling really psyched to delete a bunch of cookie code.

Aklapper removed AndyRussG as the assignee of this task.Jun 19 2020, 4:15 PM

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 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!)