Confirmed users
595
edits
No edit summary |
|||
| Line 60: | Line 60: | ||
* On idle: larger chunks, but only once near idle start, we don't want to rely too much on idle because on mobile devices it could be an unreachable state. Also we don't want to hit idle hard to avoid stressing mobile and laptop batteries. | * On idle: larger chunks, but only once near idle start, we don't want to rely too much on idle because on mobile devices it could be an unreachable state. Also we don't want to hit idle hard to avoid stressing mobile and laptop batteries. | ||
* On shutdown: avoid this at all if possible, but we have to take in count privacy. | * On shutdown: avoid this at all if possible, but we have to take in count privacy. | ||
* On pref changes: if the user changes expiration prefs, we should try to satisfy his choices. this could be done increasing the number of entries expired in background till we reach a good point of cleanup, then going back with usual expiration values. | |||
== Visits expiration algorythm == | == Visits expiration algorythm == | ||