Two underscores. That is the whole distance between a Skyrim in-joke and eighteen months in a Nova Scotia prison.
Investigators in Dane County, Wisconsin were looking for a Kik user called “fus__ro_dah.” The subpoena they sent asked Kik about “fus_ro_dah.” One underscore, not two. Last week the Nova Scotia Court of Appeal overturned the conviction that followed, writing that Brandon Klayme “is factually innocent of the offences. He should never have been charged, let alone convicted.” He had already served the full term.
The reflex is to file this under typo, and it was one. But typos are supposed to be survivable — that is the entire premise of putting a warrant, a defense lawyer, and a trial downstream of a police keystroke. What made this one fatal is that the bad identifier got more credible at every handoff, and nothing in the chain was built to re-read the string.
Follow it. Kik matched the one-underscore name and returned an email address. Google tied that address to an IP in Canada. Halifax Regional Police took the IP to Bell Aliant, which matched it to a subscriber’s home. A judge issued a search warrant on that home. By the time officers were carrying laptops out of Klayme’s bedroom, four institutions had independently confirmed the target, and all four had answered accurately. They were answering a question about a string nobody had checked since it was typed.
Four confirmations, one source. That is not corroboration. It is an echo.
Then came the part that should have stopped it. The devices were clean. No images, no messages, nothing tying Klayme to the girl — investigators could not establish he had used Kik at all during the months in question. That is not thin evidence of guilt. That is evidence of the wrong man. It was read as the first thing. He was charged on three counts, convicted at trial in 2023, and sentenced in 2024.
The honest objection is that this indicts one officer, not a system: somebody miscounted underscores, and everything after is downstream of a single careless keystroke. Concede it. Bad inputs are ordinary, which is exactly why the process carries adversaries. But the defense missed it too, and the trial judge never saw it, because the discrepancy was never put in front of him. Klayme’s own team found it — late in the appeal, after he had finished the sentence.
In the latter stages of preparing my appeal arguments, it was discovered that the subpoena contained a subtle mistake that changed the course of my life. … This discrepancy went completely unnoticed at the trial. It was never brought to the attention of the trial judge.Ars Technica
The court is blunter about the gap than anyone involved managed to be at the time: the username information was “available at the time of the trial,” and there is “no evidence confirming or explaining how it went unnoticed.” The adversarial layer did not weigh the identifier and get it wrong. It never examined it. Provenance was somebody else’s job four steps back, and four steps back it had been a fresh, unverified guess.
Anyone who has chased a bug through a stack knows this shape. The failure is never where the alarm fires. It is in the input three layers up that everyone trusted because the systems below it agreed — and they agreed because they were all reading the same value. Consensus among consumers of one string tells you nothing about the string.
The man police were actually looking for, the court now says, has a first name of Jay and an IP address in California. Eight years on, nobody has knocked on his door. The one search that would have found him was run correctly, at the right service, with the right warrant — for the wrong name.