uuidv7
for backend engineers, database architects
Why this scored 16
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Outlook
low confidence · estimate, not a guarantee7-day
~0
range 0–12
14-day
~0
range 0–14
30-day
~0
range 0–19
Signal history
7-day window (free)projected trajectory (estimate, not a guarantee)
The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 130
UUIDv7 doesn't have the properties you think it does
Explains why UUIDv7 lacks expected distributed-system guarantees. · for backend engineers
lobstersSteady 2 · same storydata3d ago - 217
UUIDv7: Timestamps aren’t time-ordered and other oddities
UUIDv7's non-monotonic timestamps can break systems expecting ordered IDs. · for backend engineers, database architects
hackernewsSteadydata1d ago