About
Why it matters
Just Human answers a simple question: when so much text is generated, how do you show that you wrote something yourself?
It records every keystroke, pause and correction as you type, and turns them into a replay anyone can watch. Real writing is full of backspaces and second thoughts. That process is the evidence.
How the score works
Each replay is scored from 0 to 100 on nine typing signals, plus a check of the browser for automation tools. The score is calculated on our server from the raw keystroke data.
- Typing rhythm
- Speed varies the way a person’s does, not at a machine-steady rate.
- Corrections
- Mistakes are made and fixed quickly, without stopping to think.
- Pasted text
- How much of the text was pasted in rather than typed.
- Thinking pauses
- Breaks to think, usually between sentences.
- Timing pattern
- Mostly short gaps between keys, with a long tail of slower ones.
- Letter pairs
- Common letter pairs are typed at a steady, practised speed.
- Bursts and pauses
- Typing comes in word-sized bursts with pauses between them.
- Key hold time
- Keys are held down for a human length of time, not close to zero.
- Slowing down
- Speed eases off over a longer writing session.
- Browser check
- Looks for automation tools in the browser. Not a typing signal.
The score is an indicator, not a verdict. The replay is the evidence.
Dictation software, accessibility tools and mobile keyboards can produce unusual patterns that lower a score. Recordings too short to analyse are not scored, and every replay stays viewable whatever its score.
By the numbers
- Times used
- 625
- Characters typed
- 130.8K
- Pages written
- 105
- Replays watched
- 5,578
Anti-bot defences
Several layers make faking a recording expensive.
- Event integrity check
- The server replays every event from scratch and rejects the recording if it does not reproduce the final text. Duration and character count are calculated on the server.
- Rate limits
- Submissions are limited per IP address, per hour and per day. We store a salted hash of the address, never the address itself, and delete these records after 24 hours.
- Browser checks
- We look for signs of automation tools, such as the webdriver flag. These lower the confidence of the analysis but never block a submission.
- Typing biometrics
- How long each key is held and the gap between keys, recorded with the physical key pressed, make typing very hard to fake convincingly.
- Session activity
- We count mouse, scroll, touch, focus and visibility events while you write. Counts only, never content or positions.
- Server-side scoring
- The score is calculated on our server from the raw events when you save, not in your browser.
We never reject a recording because of its score. A determined attacker can defeat any behavioural analysis; the aim is honest confidence, not perfect detection.
Built by Dynamic Strategies
A development and research firm building tools at the intersection of finance, technology and the open web. Get in touch or find us on X.