read error @memorization:keybase.io <=> @contechtext:twitter.com

Read error profiling https://twitter.com/contechtext/status/1060360592706469889 myself|myselfie*.

(http://web.archive.org/web/20181110231537/https://twitter.com/contechtext/status/1060360592706469889 is good (for my shexy [..or is that 'shhexy'? [SHA-256](https://en.wikipedia.org/w/index.php?title=SHA-256&redirect=no)?] complexion) from another angle.)

^{*[twitter.com/DataSelfie](https://twitter.com/DataSelfie), [github.com/d4t4x/data-selfie](https://github.com/d4t4x/data-selfie)}

Sigchain/Blockchain:
````
https://keybase.io/memorization/sigchain#a685bb49067a6ad7f5b4ef1de974610aedf83479a93c39b8f6c1dea03535f5840f
````

Clickable link for alpha/older/legacy/young/broken/beta (https://en.wikipedia.org/wiki/Lynx_(web_browser)) browsers: https://keybase.io/memorization/sigchain#a685bb49067a6ad7f5b4ef1de974610aedf83479a93c39b8f6c1dea03535f5840f (Do not mind the always-triggering https://en.wikipedia.org/wiki/Hexspeak, it is how computers and computer people actually signal/sigtalk, I do not *even* want to mention "https://t.co/ZNyMpX35id" the staggeringly abbreviated sigchain proof URL version Twitter used to describe Keybase there, we "have to speak that way" to use www.Keybase.io.)

Emailchain:

> From: Keybase
> To:sew@iSew.info
> Subject: your twitter (@contechtext) proof
> Date: Fri, 9 Nov 2018 20:48:17 +0000
> X-SES-Outgoing: 2018.11.09-54.240.8.176
> Feedback-ID: 1.us-east-1.35Qs6oTJqJlRBp8zjxXYfyo2dyykpOoKW188Wk5KQ30=:AmazonSES
> ------=_Part_361483_535652878.1541796497716
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit
>
> Hi, memorization,
> your attempted twitter identity proof of @contechtext never succeeded. We've been checking it repeatedly
>
> ...
>
> If you think there's a bug, please post an issue on our github tracker, linked in the footer of the site.
Include the link to your proof.
>
> ...
>
> Thanks! -Keybase

Pseudocode:

`id.read.error (memorization, contechtext)`

The title uses "`m.user`" https://matrix.org/specification, I mean https://matrix.org/docs/spec formatting, for reader (going between Keybase and Twitter) clarity.

Translationchain:

Keybase.io had some trouble reading Twitter.com: https://keybase.io/memorization/sigchain#a685bb49067a6ad7f5b4ef1de974610aedf83479a93c39b8f6c1dea03535f5840f is shown https://twitter.com/contechtext/status/1060360592706469889.

Keybase.io did not like how it read Twitter.com: https://keybase.io/memorization/sigchain#a685bb49067a6ad7f5b4ef1de974610aedf83479a93c39b8f6c1dea03535f5840f is shown https://twitter.com/contechtext/status/1060360592706469889.

Keybase.io had a problem reading Twitter.com: https://keybase.io/memorization/sigchain#a685bb49067a6ad7f5b4ef1de974610aedf83479a93c39b8f6c1dea03535f5840f is shown https://twitter.com/contechtext/status/1060360592706469889.

Start by reviewing the linked Twitter proof and Keybase sigchain entry, then determine what read error is reproducible and what behavior is expected. The issue names no source files, tests, or entry points, so identify the relevant proof-handling area before defining a regression test and a clear completion condition.

Written by the indexing model from the issue text.