Website fails to verify message generated by command line

I have yet to understand what one can put into the website "verify" box and have it do anything.

Here is test message signed by command line:

```
keybase sign -m test
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkP1syTF jT3tRJg4Uxp3oT8 kJfrPewpPTFpseI gCj3EZDG0DErOh0 2H7uFRqv8DoXPRY tiPWx1pXQT0x23f RiqF29o1nTgAkK7 oQRPA4N1aAo5inD TKKL2igrfcpKQMo CzuElFovhC5NT0m 3co04Lc4nVyibws v0QTpUJSXTQ. END KEYBASE SALTPACK SIGNED MESSAGE.
```

Command line `verify` works:

```
keybase verify -m "BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkP1syTF jT3tRJg4Uxp3oT8 kJfrPewpPTFpseI gCj3EZDG0DErOh0 2H7uFRqv8DoXPRY tiPWx1pXQT0x23f RiqF29o1nTgAkK7 oQRPA4N1aAo5inD TKKL2igrfcpKQMo CzuElFovhC5NT0m 3co04Lc4nVyibws v0QTpUJSXTQ. END KEYBASE SALTPACK SIGNED MESSAGE."
Signature verified. Signed by latkin (you).
test
```

Website claims it doesn't even understand what the message is:


Start by reproducing the supplied signed message in the website's verify box and compare the result with the command-line verify output shown in the issue. Trace the website verification entry point and determine why this valid message is rejected; done means the website accepts it, identifies the signer, and displays the verified content.

Written by the indexing model from the issue text.