3 ms·
You may want to consider a keep-alive strategy based on usage and not an arbitrary static timeout. What if I need my checklist for 7.5 days? A corollary is that
by edfletcher_t137 2y ago
You may want to consider a keep-alive strategy based on usage and not an arbitrary static timeout. What if I need my checklist for 7.5 days? A corollary is that this may reduce your overall data usage as a lot of people may create a list and immediately abandon it. If you can expire those in less than 7 days, you're saving.
- millhouse1112 2y agoGood idea. It's simple to track this. What idle duration limit makes sense for deletion?
- edfletcher_t137 2y agoThat's a great question! And fortunately, one where you can use human behavior as a guide: if someone is actively using a checklist it seems reasonable to presume they're at least accessing it once a day. So as a quick first-pass, double that time period to two days. Also start collecting usage metrics and mine those in the future to further refine this number.
- stanmancan 2y agoUser initiated; maybe some arbitrarily long duration measured in years.
- nbk_2000 2y ago90 days since last view, or 1 year if you can afford to be generous. For "slow burn" projects with other people checklists easily go longer than a week without being looked at.