cp/m68k
for os devs
Why this scored 0
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.
- 113
CP/M-386: CP/M for 386 protected mode, derived from CP/M-68K
new os for 386 protected mode · for os devs, retrocomputing enthusiasts
lobstersSteadyhardware42d ago - 212
CP/M-68K emulator
Retro emulator available · for retrocomputing enthusiasts
lobstersCoolingother47d ago - 38
CP/M-386 – CP/M for 386 protected mode, derived from CP/M‑68K
CP/M-386 released · for os devs
hackernewsSteadydevtools42d ago