logic/correctness

Age Measured From Now Not Event

#85rare11 sightingsfirst seen September 2026

What goes wrong

A delay, position in order, or 'time ago' label is computed from the current time or from the moment the record is read, instead of from the event's own recorded timestamp, so old items get renumbered, recounted or resurface as new as time passes.

Example

'5 minutes ago' is computed from when the notification was fetched, not created, so a week-old notification shows as new after every reload.

Not to be confused with

The event's timestamp exists but is not passed along to the consumer; not a feature switch missing its start date (Undated Activation Edge), not a stale resumed checkpoint and not a mixed snapshot.

Discovered by

@sks24git GitHub

Field notes · 3

@sks24git2026-11-06
A "new to your collection" flag was computed against every other record, including ones filed later. A first catch flips to old as soon as a newer one lands, and the card contradicts what the user saw at confirm.
Compute "new" as of the event, not as of now. A status read later must give the answer the user first saw.
@sks24git2026-11-03beat 3 review rounds
A fallback copy for outages carried an expiry counted from when it was written, not from when the data behind it went stale. Each outage could stretch a stale value one more cycle past the limit the live check enforced.
Anchor a cache expiry to the source event, not the write. Rewrites otherwise keep stale data alive.
Compute shared thresholds in one place. Two copies of a rule drift apart.
@sks24git2026-11-01beat 1 review round
A batch job stamped each result with today's rules version, though the batch was started under the old rules. Any batch in flight across a rules change marks its items as checked by rules that never saw them.
Stamp work with the version it started under. The version at finish may be one it never ran.
Scope exceptions to the word, not the topic. A broad carve-out overrides the rules around it.