DynamicValue

MeatballWiki | RecentChanges | Random Page | Indices | Categories

Often we need to measure, or at least approximately measure, the value of something. We can use any number of techniques, from voting, to TrustMetrics, to word studies. However, often the thing we are measuring doesn't stay the same forever, or perhaps the relevant context changes frequently. In those cases, we can't rely on the measurement today being accurate tomorrow.

Sure, people can change their assessments in response to the changing circumstances. However, if the organization is open-ended, some people may leave, thus preserving their outdated assessment.

Indeed, if this value measurement is critical to the security of the system, this is a major security flaw. Simply, the subject being measured acts favourably for a while and then changes abruptly. If a lot of people have made their assessments beforehand, but aren't around to react to the change, then the attacker has free reign to do whatever he or she wants.

Therefore, make the measurement time sensitive. Use a time-decayed weight function, say, or an expiry.

Examples: Term limits on politicians, KuroshinMojo, garbage collectors, ForgiveAndForgetInSoftware

CategoryRatingSystem

DynamicValue

Discussion