playjson
for scala backend devs
Why this scored 7
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
medium confidence · estimate, not a guarantee7-day
~8
range 0–20
14-day
~8
range 0–23
30-day
~8
range 0–27
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.
- 115
Play Framework's Json.format not working with our models after upgrading to Scala 3?
Json.format issue after upgrade · for scala devs
stackoverflowSteadydevtools47d ago - 215
Read and write a LocalDateTime in a JSON object using a custom date/time format
Guide to custom LocalDateTime serialization in Play JSON for Scala applications. · for scala backend devs
stackoverflowSteadydata9d ago