The replay file format
A replay is a plain JSON file anyone can read, so a reader never has to take this site's word for anything. This page describes version 1 of the format and the rules behind every figure the reader shows.
The file
Replay files are UTF-8 JSON and end in .writing-replay.json. The editor writes one edit per line, so a file is easy to read in any text editor.
{
"format":"writing-replay",
"version":1,
"how_to_open":"Open https://theguysaccount.github.io/proof-of-human-writing/verify/ and choose this file ...",
"app":"https://theguysaccount.github.io/proof-of-human-writing/",
"title":"My essay",
"author":"Sam",
"exported":"2026-11-10T08:31:00.000Z",
"tick_ms":50,
"final":{"length":687,"sha256":"1752c748…"},
"sessions":[
{"start":"2026-11-09T19:02:11.000Z","events":[
[114,0,0,"T"],
[3,1,0,"h"],
[7,2,0,"PASTED TEXT",2],
[4,12,11,""]
]}
]
}
Fields
formatis always"writing-replay".versionis an integer; readers refuse versions newer than they understand.titleandauthorare whatever the writer typed, if anything. Nothing checks them.exportedand each session'sstartare ISO 8601 times from the writer's device clock.tick_msis the timing unit, 50 milliseconds.finalgives the length and the SHA-256 (of the UTF-8 bytes) of the text the edits should produce. The reader replays every edit and compares. A mismatch means the file was changed or damaged after export.sessionslists the sittings in order. Each has astarttime and itsevents. A later sitting continues from the text the earlier ones left.
Edits
Each event is [dt, pos, del, ins] or [dt, pos, del, ins, origin]:
dt: ticks since the previous edit in the same sitting (sincestartfor the first).pos: where the edit happens, counted in UTF-16 code units from the start of the text.del: how many code units are removed atpos.ins: the text inserted atpos.origin: how the browser reported the change. Leaving it out means 0.
| Origin | Meaning | Browser input types |
|---|---|---|
| 0 | one key press: a single character, or a deletion | insertText, insertLineBreak, deleteContentBackward and other insert…/delete… types |
| 1 | several characters at once from the keyboard | the same types with more than one character (word suggestions, swipe typing, dictation, insertReplacementText) |
| 2 | paste | insertFromPaste, insertFromPasteAsQuotation, insertFromYank |
| 3 | drag and drop | insertFromDrop |
| 4 | undo or redo | historyUndo, historyRedo |
| 5 | a change with no trusted keyboard event | changes made by scripts or extensions, events the page itself generated, and unknown types |
Input types are defined in the W3C Input Events specification (MDN summary). The editor reads them from the browser; it never sees which keys were pressed.
How the reader marks the finished text
Each character of the finished text carries the origin of the edit that inserted it. One exception: when a paste, drop, undo or redo inserts text that was already in the document, or was removed from it earlier in the recording, the inserted characters keep the marking they had. That way a writer moving their own sentence around isn't counted as pasting, and pasted text copied a second time is still marked as pasted.
How the figures are worked out
- Writing time adds up the gaps between edits within each sitting, leaving out any gap longer than 60 seconds.
- Keyboard, pasted and other shares count the characters of the finished text by marking: keyboard is origins 0 and 1, pasted is 2 and 3, other is 4 and 5. Percentages are rounded, but a share that isn't zero is never shown as 0%, and one that isn't everything is never shown as 100%.
- Typing rhythm uses the gaps between consecutive single-key insertions, up to 2 seconds apart. “Very even” means their coefficient of variation (standard deviation divided by mean) is below 0.3, over at least 150 gaps.
- Continuous runs count keyboard characters entered with no gap longer than 5 seconds. A run of 1,000 or more characters with no pause over 10 seconds in the whole recording is pointed out.
- Corrections: when at least 500 characters were entered and less than 1% of them were later deleted, the reader points it out.
- Bulk keyboard insertions of 40 or more characters at once are listed with pastes.
These are heuristics, chosen to point a reader at moments worth a look. None of them, alone or together, is a verdict, and the reader never shows a score.
Replay links
A link is https://theguysaccount.github.io/proof-of-human-writing/verify/#r= followed by the file's exact bytes, compressed with raw DEFLATE (RFC 1951) and encoded as base64url without padding. The editor only offers a link when the result is short enough to survive being pasted into chat and mail apps.
Fingerprint
The fingerprint is the SHA-256 of the file's bytes. Writer and reader see the same one when the file arrived unchanged.
Reference code
The format, the analysis and its tests are in core.js, which runs unchanged in the browser and in Node.js. Use it, or write your own reader: the format is open and the code is MIT licensed.