Archived
Recovery minted the replacement code twice — one sent to the account service, a different one wrapped into the identity record and shown on screen. The first recovery looked perfect and left the account openable only with a code nobody had ever seen. It takes a second recovery to notice, which is to say it would have been noticed by somebody who had already lost a passphrase twice. One code now reaches both writes. The passphrase and recovery-code fields never told the keyboard what they were, so autocorrect was live on both. A passphrase is chosen to be long and memorable rather than dictionary-shaped, which is exactly the sort of text autocorrect likes to improve, and an improved passphrase cannot be recovered — only replaced with the code. The recovery code is twenty-eight characters of base32 typed once, from paper, under stress. Both now declare themselves, and the handle no longer gets a capital letter it never asked for. The recovery code is also laid out four groups to a line: left to wrap, the last group split across lines as "…-YR" and "RK", on the one screen somebody copies by hand with no way to check it afterwards. Rows this device can read now come before the ones it cannot. An area is shared by everyone cleared for it, so the listing carries other people's files as rows without names — showing them is deliberate, but arriving at a screenful of "Encrypted for another key" with your own folder below the fold is a poor way to meet the thing. The instrumented suites are new: registration, sign-in, recovering twice, folders, upload, share links with the secret asserted to be in the fragment, switching areas within a clearance, and a visual tour that photographs each screen. Shared helpers live in one file, because the same row-finder was copied into three and then fixed in one of them — and the first version scrolled inside a `waitUntil`, which ran on the main thread often enough for Android to declare the app unresponsive and kill the run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>