nodepostgres
for backend developers, node.js engineers
Why this scored 10
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
Signal history
7-day window (free)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.
- 134
How to configure pg to work natively with Temporal.PlainDate?
Shows how to configure node-postgres to natively handle Temporal.PlainDate values. · for backend developers, node.js engineers
stackoverflowSteady 4 · postgresdata40d ago - 214
Postgres row-level security leaks across tenants when using a pooled connection
Highlights RLS leakage when using pooled connections across tenants in PostgreSQL. · for backend engineers, DBAs
stackoverflowSteadysecurity48d ago