Closed MerlinLaffitte closed 4 years ago
There is already a basic protection here: https://github.com/faameunier/tk-chrome/blob/93a60e6f5ad3f92bab761f487e8ddce3a6365f84/src/services/scorer.js#L45-L50
It definitely can be improved (maybe add a exp decay in the score from max score to 1 ?) Same applies for protection after restore or next ?
We could also move these logic to the abstract class as I don't think it will change depending on the scorer, but that's for a V10
closing this as last_active_timestamp
is now initiated at creation time and when restored (PR #63)
What
How
created_at
attribute for tabs in order to handle deletion onmax(last_active_timestamp ,created_at)
Why