@ori mentioned that we should try to cut down on our cookie habit, and put stuff in localstorage instead. Apparently the ResourceLoader issue was fixed, that was filling the storage.
Cookies are expensive because they're sent back and forth on every pageview.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Krinkle | T110353 Audit use of cookies | |||
| Open | None | T108849 Move CentralNotice stuff out of cookies | |||
| Resolved | • AndyRussG | T117650 CentralNotice: use KVStore instead of cookies for mixins that create cookies, except for Fundraising | |||
| Resolved | None | T19108 Make "Hide" cookies for CentralNotice notice-independent | |||
| Declined | None | T131317 Spike: Break out tasks for "Move CentralNotice stuff out of cookies" | |||
| Resolved | • AndyRussG | T131319 CentralNotice: Make a plan for moving stuff out of cookies | |||
| Open | None | T132640 CentralNotice: Slurp up existing wild cookies and copy them to LocalStorage or delete them | |||
| Resolved | • AndyRussG | T132639 CentralNotice: Use LocalStorage instead of cookies whenever possible, for buckets, impression limiting and large banner limiting | |||
| Open | None | T135090 CentralNotice: finalize list of wild useless cookies for slurp, and push config change | |||
| Resolved | ori | T132374 Generate a list of junk CN cookies being sent by clients |
Mostly fixed, according to https://lists.wikimedia.org/pipermail/centralnotice-admins/2015-November/000056.html
There is some progress! Unfortunately there are two big areas still to work on for this: bucket cookies and hide cookies. While we do have a viable LocalStorage-based replacement mechanism in place, we also need to check what sort of fallback mechanism, if any, would be needed, at least for Fundraising.
@AndyRussG, what is the status of this work? I just checked and on enwiki I currently have eight(!) cookies from CentralNotice:
@ori thx for the ping! It's not currently programmed for the near future, but I think we should be able to bring it in. I'll talk to folks and get back to you. :)
I'd love to what proportion of our visitors have LocalStorage-capable browsers. Falling back to cookies for the ones that don't support LS seems problematic because these are probably older systems to begin with. Are we considering a non-cookie fallback?
Are we logging local storage failures now? Browser support is looking pretty good on caniuse, but I dunno how many people disable it via some method. http://caniuse.com/#feat=namevalue-storage. Total Opera mobile looks like less than 1% of our views on https://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm
Removed story points because this is now a tracking task (See blocked-by for subtasks.)