ipv4
for network engineers, sysadmins
Why this scored 18
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.
- 116
RFC8950: Announce IPv4 with an IPv6 next-hop
New RFC enables announcing IPv4 routes with IPv6 next-hop, impacting routing implementations. · for network engineers, sysadmins
hackernewsSteadyother10d ago - 211
A Farewell to ARPs: IPv4 Service on IPv6-Only Networks
Improves network service · for network admins
lobstersSteady106d ago