Keybase diagnostic messages on proof breakage

As Keybase is geared moreso towards the technically inclined, I find it rather annoying that we're given nothing but "Keybase is watching for your proof" messages when something goes awry. We should have an option to see exactly what Keybase sees when it attempts to view the proof. That way we can see if there is an SSL error (I, for instance, have rather strict cipher settings), and many "simpler" clients such as Links and some HTTPS libraries for various languages, do not fully support the cipher requirements I have in place, even though most (if not all) modern browsers have no problem with them at all. As such, the connection may work flawlessly in a browser and fail for Keybase. (This has yet to be the case, but it is an example of when debug information would be beneficial for everyone).

Likewise, I have 301 redirects in place to force SSL and prepend www to most of my domains. While they work fine in my browser, there may be a time when the Keybase software does not cooperate with the server and complains about a broken proof.

I think that allowing us the option to see additional information, such as a traceroute, ping, or the HTTP headers that result from Keybase attempting to validate a proof, would go a long way in cracking down on the number of complaints you guys get when we can't validate a given proof. This way, we can troubleshoot it more on our own before resorting to complaining.

The issue names no files or tests; start by locating the Keybase proof-validation entry point and where failures become the generic status message. Define the diagnostic scope around SSL errors, redirects, and HTTP response details, then document the failure cases that must be observable when the work is complete.

Written by the indexing model from the issue text.