Keybase website - twitter direct message integration

Recently twitter announced that they're going to be increasing the [character limit for direct messages to 10,000 characters](https://twittercommunity.com/t/removing-the-140-character-limit-from-direct-messages/41348). This actually makes it a little more viable platform for direct encrypted messaging that a lot of people use, and keybase already allow you to 'verify' your twitter identity.

What I'm suggesting is that if you're using the keybase website, on the 'encrypt page' there be a button next to 'Encrypt' that says 'Encrypt & Twitter DM' or something catchier. you already know the recipient from the recipient field and it would send the encrypted text via one click instead of that extra bit of copying and pasting.

As for the receiving of encrypted twitter messages, that too would be great but you'd need some sort of dedicated 'received encrypted messages' page. I really like keybase, but I think just adding these things that would allow for a bit less of a roadblock from a UI perspective of copying and pasting could really help Keybase take off.

A sort of expanded version of the abandoned project [CrypTweet](https://github.com/mpesce/CrypTweet) but with less reinventing the wheel that was necessary at the time :).

I know a lot of things here focus on the API, but the website really is quite slick but could be slicker and it'd be great from a 'for the masses' perspective to make it as easy to use as possible.

Start at the website's “encrypt page” described in the issue and review how the recipient field and Encrypt action currently work. Assess the proposed Twitter DM sending flow and the separate received-messages page, then define the scope and acceptance criteria before implementation; the issue does not name files or tests.

Written by the indexing model from the issue text.