- 5/27/2026
- Updated 5/27/2026
Server-Validated Quotes Typing: Why Scores and Collections Are Trustworthy
Quote chain and timed quotes use server sessions and submit_test_result validation—the same integrity model as other Type Faster tests. Learn what that blocks.
Sessions start on the server
Chain mode calls `start_quotes_chain_session` on first keystroke. The server stores prompt text, start time, and quote id—clients cannot invent a shorter passage.
Submissions go through `submit_test_result`, which recomputes timing and accuracy instead of trusting posted JSON.
Read the attribution tail before you sprint the quote body; most not-counted lines fail on the author name.
Read the attribution tail before you sprint the quote body; most not-counted lines fail on the author name.
What cheaters cannot do
Forging WPM with a REST client fails when duration and character totals disagree with the stored prompt.
Inflating collection counts without perfect server accuracy fails for the same reason—collection flags are set inside the validated submit path.
Pair three chain lines on busy days with one standard one-minute test on Fridays for employer-comparable numbers.
Slow punctuation drills on `/test/punctuation` when commas and nested quotes break before names do.
Credibility as product philosophy
Type Faster treats honest measurement as a core feature across modes: standard tests, hiring screens, specialty keyboards, and quotes.
Read ANTI_CHEAT_SYSTEM.md in the repo if you want the full list of limits, drift logging, and rate rules—quotes now sit in that same table.
If API errors mention missing RPCs, apply quotes migrations in Supabase before blaming your keyboard.
When a line looks perfect but does not count, assume keystroke accuracy—not only final-line color—before you retry.
Continue practicing
This cluster is about attributed quote lines and collection goals. Open quote chain for milestones and perfect-line collection, run 60s timed quotes for WPM, then check the famous quotes leaderboard (timed runs only).